Frootmig

Thanks for the reply gr5, I havce checked all of the network settings and they have not changed, the 502 error is generally an issue with the sending server, the firmware was updated to the latest 8.2.1 before it arried and was working fine, I think the camera issue is directly related to the issue of the connection to Cura dropping after a few seconds, I cannot keep the connection from the S5 to Cura stable for more than a few seconds. The conneciton between the S5 and the PC with Cura installed is a direct network connection on the same network subnet with nothing inbetween to block any ports. I am at a bit of a loss at the moment, I am thinking of trying a backgrade to an earlier firmware version to see if that helps.

Hi, We have an Ultimaker S5 on firmware V8.2.1, it is connected to our ehternet network and assigned an IP address by DHCP which is fixed using a DHCP reservation, until a few days ago the machine was talking fine with Cura and I was able to browse to the IP address to view the camera, but since last Tuesday we have not been able to get a reliable connection over the network to Cura and when I browse to the Management Console from the web interface I am unable to view the camera and I only get a "502 Bad Gateway" error, I am able to browse to the other pages such as the logs, API and temerature graphs, I assume this error is probably the cause of the error connecting to Cura as well. Has anyone seen an error like this before, I have searched though the help docs and community and I can see plenty with network connection issues but not this specific error, any help would be gratefully accepted Many thanks Frootmig