Highlighted

Coldfusion 2016 Websocket only responding locally

New Here ,
Jan 05, 2018

Copy link to clipboard

Copied

We have a websocket setup on an internal network 192.16.1.x IP addresses.  The server is running CF 2016 Updated to the latest patch as of this post.  We have a controller/publisher that was being run from an iPad and listeners/subscriber computers.  A user clicks through the site on the iPad and the displays update.  This worked until a week ago.

Attempting to run Chrome on the server and open the controller URL using the 192.168.1.10:8500 URL (using ColdFusion's internal web server for simplicity) never updates the displays.  If I call the same URL changing to the local IP, 127.0.0.1:8500 then all of the displays/subscribers get their updates.

I opened several Chrome browsers on the server itself pointing one to the controller and the others to the same URLs as the displays would use, i.e. 

192.168.1.10:8500/index.cfm?mychannel=channel1, 

192.168.1.10:8500/index.cfm?mychannel=channel2, 

192.168.1.10:8500/index.cfm?mychannel=channel3

Calling the servers IP address will not update any subscribers.  No failure messages logged.  If I hit 127.0.0.1:8500, it will update all of the displays and even the Chrome browser windows I have open on the same server.

Running on Windows 2012R2, firewall is disabled.  Any thoughts or suggestions?

Views

158

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Coldfusion 2016 Websocket only responding locally

New Here ,
Jan 05, 2018

Copy link to clipboard

Copied

We have a websocket setup on an internal network 192.16.1.x IP addresses.  The server is running CF 2016 Updated to the latest patch as of this post.  We have a controller/publisher that was being run from an iPad and listeners/subscriber computers.  A user clicks through the site on the iPad and the displays update.  This worked until a week ago.

Attempting to run Chrome on the server and open the controller URL using the 192.168.1.10:8500 URL (using ColdFusion's internal web server for simplicity) never updates the displays.  If I call the same URL changing to the local IP, 127.0.0.1:8500 then all of the displays/subscribers get their updates.

I opened several Chrome browsers on the server itself pointing one to the controller and the others to the same URLs as the displays would use, i.e. 

192.168.1.10:8500/index.cfm?mychannel=channel1, 

192.168.1.10:8500/index.cfm?mychannel=channel2, 

192.168.1.10:8500/index.cfm?mychannel=channel3

Calling the servers IP address will not update any subscribers.  No failure messages logged.  If I hit 127.0.0.1:8500, it will update all of the displays and even the Chrome browser windows I have open on the same server.

Running on Windows 2012R2, firewall is disabled.  Any thoughts or suggestions?

Views

159

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Jan 05, 2018 0

Have something to add?

Join the conversation