# Can not access to port 1935 when connections per protocol are over 65535 **URL:** \ **Category:** Wowza Developer Dojo\ **Tags:** wowza-streaming-server-java-api\ **Created:** [July 1, 2016, 10:57am UTC](https://community.wowza.com/t/can-not-access-to-port-1935-when-connections-per-protocol-are-over-65535/46948 "2016-07-01T10:57:23Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Danh\_Nguyen\_Cong](https://avatars.discourse-cdn.com/v4/letter/d/85e7bf/32.png) [@Danh\_Nguyen\_Cong](https://community.wowza.com/u/Danh_Nguyen_Cong)\ **Post date:** [July 1, 2016, 10:57am UTC](https://community.wowza.com/t/can-not-access-to-port-1935-when-connections-per-protocol-are-over-65535/46948/1 "2016-07-01T10:57:23Z")
I protect my streaming using SecureToken. When the token is invalid the connections using that token are rejected. But in the monitor still increase connection. When it increase to 65535 connections I can’t access to port 1935. If I restart the wowza server, I can reconnect to port 1935. Is there anybody get the same problem? Help me! Thanks. ---
**Author:** ![Danh\_Nguyen\_Cong](https://avatars.discourse-cdn.com/v4/letter/d/85e7bf/32.png) [@Danh\_Nguyen\_Cong](https://community.wowza.com/u/Danh_Nguyen_Cong)\ **Post date:** [July 4, 2016, 11:02am UTC](https://community.wowza.com/t/can-not-access-to-port-1935-when-connections-per-protocol-are-over-65535/46948/2 "2016-07-04T11:02:34Z")
This is my solution for this problem. I have written any IP address and connection time into a log file. After that I view that file log and find some IP have connection in top highest. Because my OS is Linux I drop the IP addresses by the iptable commands. The connections to my server have decreased very fast. ---
**Author:** ![sal\_jefferson](https://avatars.discourse-cdn.com/v4/letter/s/6de8d8/32.png) [@sal\_jefferson](https://community.wowza.com/u/sal_jefferson)\ **Post date:** [July 15, 2016, 6:20am UTC](https://community.wowza.com/t/can-not-access-to-port-1935-when-connections-per-protocol-are-over-65535/46948/3 "2016-07-15T06:20:49Z")
Thank you for updating this post and providing a workaround. Glad you were able to sort this out. Regards, Salvadore