– look at the router, delete dhcp ip adress for uradmonitor. Than reconnect.

– If you have a Fritzbox that make problems…

– test at another router.

Peter

Yep, defintitely server side, look at the originiating IP address in Wireshark.

Although code 400 is for bad client side data sent. Corrupted packets?

Indeed very odd. Tried another PSU?

I’m afraid there were no updates. So the change must have been local. Yes, currently there are several IP used. The one for data is correct: 23.239.13.18.

Lars, just as a note, I don’t think this is physical, nevertheless if you are unable to find the problem, you can send the unit back anytime to get a replacement.

Here is a snapshot of the access log. Because the packets are not landing on data.uradmonitor.com, the server issues a HTTP 400.

As the unit is unable to get a valid reply, it auto-resets after 5 minutes. See the ts parameter, which is the local time of the unit in seconds, it never goes over 240 (=4×60 seconds, on the fifth it resets).

Two units are currently having this problem, 11000016 and 11000009 . I will find out why.

Good idea. Support forum created and this topic moved.

Regarding the problem, I have investigated things further. Must say this seems to be an elusive bug and I have wasted a few hours to track it already.

Apparently the two units get to the server with their User Agent info stripped. Probably other parts of the packages are changed as well. Also the source IP is null. I don’t know what on their route changes their HTTP headers. Local tests didn’t show this issue, and it is impossible to consider a malfunction of any kind.

I can only assume a firewall would be able to have this intrusive result.

With the User Agent info removed and no source IP, the server denies the packages with a HTTP 400 Error code (Bad request).

I will see what I can do about this.

• This reply was modified 9 years, 4 months ago by uRADMonitor.