# IPWhiteListing: Access from a different IP possible even tho that IP is not in the IPWhiteList
**URL:** https://community.wowza.com/t/ipwhitelisting-access-from-a-different-ip-possible-even-tho-that-ip-is-not-in-the-ipwhitelist/96811
**Category:** Wowza Streaming Engine
**Tags:** server-administration
**Created:** [January 15, 2024, 9:54am UTC](https://community.wowza.com/t/ipwhitelisting-access-from-a-different-ip-possible-even-tho-that-ip-is-not-in-the-ipwhitelist/96811 "2024-01-15T09:54:45Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Goran\_Iliev](https://community.wowza.com/u/Goran_Iliev)
#### Post date: [January 15, 2024, 9:54am UTC](https://community.wowza.com/t/ipwhitelisting-access-from-a-different-ip-possible-even-tho-that-ip-is-not-in-the-ipwhitelist/96811/1 "2024-01-15T09:54:45Z")
I set the ipwhitelist to the wowza streaming engine server ip, which is for example 192.168.2.2.
If i try to connect to manager on the same system, i can connect to the GUI. That is good.
But if I try to access the GUI (Manager) on a computer from a different subnet (subnet routing is done) it is also possible, even though i did not put the ip of this new computer in the whitelist? but i do specify the ip 192.168.2.2 under wowza streaming engine url on the new computer while trying to access. I am not sure if it is a right behaviour or not, since IPWhiteList should be checking if the access request is comming from one of the defined IPs right?
PS: On the remote client, i did not install wowza Streaming Engine Manager. I am just opeing a browser and then give the [http://192.168.2.2:8088/enginemanager/](http://192.168.2.2:8088/enginemanager/) url then give the credentials and under " **wowza streaming engine ur** l "
---
### Author:  [@Karel\_Boek](https://community.wowza.com/u/Karel_Boek)
#### Post date: [January 17, 2024, 12:23pm UTC](https://community.wowza.com/t/ipwhitelisting-access-from-a-different-ip-possible-even-tho-that-ip-is-not-in-the-ipwhitelist/96811/2 "2024-01-17T12:23:26Z")
If you set the IP address in /conf/Server.xml under /Root/Server/RESTInterface/IPWhiteList then you may be able to open the login page from the other computer, but when you try to login you should get an error, because the front-end is loading but the connection to the REST API should be blocked.