I keep getting server refused connection and wondering if the problem is with my ISP setup? I did get a significant windows update a few days ago but I can't log in with IOS on cellular either.
It also has not worked for me since the 28-Aug on any device.
I use this daily and it has been pretty rock solid until now.
I had that but it appeared to be a HTTPS/HTTP issue. Changing the URL to HTTP fixed it, revealing that my OpenEVSE hadn't uploaded anything since the evening (UK time) of Monday 26th August. Re-adding the key has made no difference, nor has soft or hard reboots of the OpenEVSE, nor has a hard reboot of the router. OpenEVSE Services tab is stuck on "Connected: No"
Yes my OpenEVSE also has not uploaded any data for at least 6 days (Australia).
I too tried putting in the API key again, which seemed to have changed.
Appears to be the same time as an update occurred as the layout, background colours, menus etc. have also changed within the online portal data.openevse.com/emoncms when it stopped working.
I can push data from other devices (such as manually via the API on HTTP, not HTTPS), but the OpenEVSE in my garage isn't sending anything... guessing it's setup for HTTPS.
I have confirmed my OpenEVSE is sending data OK to emoncms.org as i use this as a backup server.
So looks like the data.openevse.com server is down.
Just renewed the https certificates... Any better?
That's fixed the website HTTPS access. OpenEVSE is still saying "connected: no" though.
Progress is good. The login to the data server is working for viewing data but no new data is being posted and the OpenEVSE reports no connection. I generated a new device key and applied it to the OpenEVSE unit and still no connection nor updates to data.
I too am having trouble since around Aug 26th. I am still getting "Connected no" when trying to post data to data.openevse.com/emoncms.
Any idea of what changed? Surely the certificates being updated are not the root cause of this?
The new certificates allow me to get to the site, but now I have "Connected NO" and the Admin page of data.openevse is in a constant timed out condition. No amount of revalidation works.
Without changes on my part to URLs or keys, I am now sending information as of 0800h EDT.
It looks OK.