0 votes
asked in ESPaper by (180 points)
Hi, my EsPaper doesnt refresh since a week ou two.

It just display:

Device not found or access not allowed
Please configure this device on
espaper.com
HTTP CODE -1

Any hints?

Thanks!
commented by (3.9k points)
Thanks Alex, we'll take a look.
commented by (8.8k points)
The server is running. How old is your code? Earlier versions only used the finger print of the server certificate. This had the disadvantage that the device would stop working with exactly this error message once our hosting provider would renew the server certificates. Later versions of the code are using the root certificate which has a much longer expiration period. Can you please attach your espaper to your computer and provide the log output to us? Without it it's impossible to find the problem... Thank you
commented by (180 points)
Hi,

I've just uploadd the last release.

Here's my log:

WIFI_SSID = [ZAP 2.4Ghz]
9
WIFI_PASS = [XXXXX]
9
DEVICE_ID = [XXXX]
9
DEVICE_KEY = [XXXX]
10
Loaded config
State: 1


***Time before connecting to WiFi 42934
................................................................................Could not connect to WiFi


***Time before going to fetching data 52087
Creating cache marker request.json_
Getting https://www.espaper.com/public/devices/XXXX
Free Heap: 29992FS after cleanup: 753 of 957314 bytes used[HTTP] begin...
URL: https://www.espaper.com/public/devices/XXXX with fingerprint 26 8E 97 34 2D 40 55 0F 6A 76 D9 03 64 8D 1C 17 1F 12 AF E2[HTTP] GET...
[HTTP] GET... code: -1
[HTTP] GET... failed, error: connection refused


***Time before going to sleep 54008
commented by (8.8k points)
Thanks for the logs. There we have the culprit: ................................................................................Could not connect to WiFi
Did you change your SSID or your WiFi password? It seems for whatever reason the ESPaper device could not connect to the WiFi. In the past I have seen that the ESP8266 had problems with SSIDs containing a space. Also recently in my home network the ESP could connect to one SSID but not to the other. Do you have the chance to try another SSID or WiFi network in general?
commented by (180 points)
edited by
I just renamed my Wifi SSID but same error:

WIFI_SSID = [XXXX]
9
WIFI_PASS = [XXXX]
9
DEVICE_ID = [XXXX]
9
DEVICE_KEY = [XXXX]
10
Loaded config
State: 1


***Time before connecting to WiFi 477
................................................

***Time before going to fetching data 6323
Creating cache marker request.json_
Getting https://www.espaper.com/public/devices/XXXX
Free Heap: 29920FS after cleanup: 753 of 957314 bytes used[HTTP] begin...
URL: https://www.espaper.com/public/devices/XXXX with fingerprint 26 8E 97 34 2D 40 55 0F 6A 76 D9 03 64 8D 1C 17 1F 12 AF E2[HTTP] GET...
[HTTP] GET... code: -1
[HTTP] GET... failed, error: connection refused


***Time before going to sleep 8697

1 Answer

0 votes
answered by (3.9k points)
selected by
 
Best answer
At this point we feel confident posting an answer rather than a comment.

Contrary to your first comment the second one shows that the device successfully connected to your WiFi (by the absence of a "Could not connect to WiFi" message). However, as Dani pointed out in his first comment you seem to be running an older version of our ESPaper client.

As per your debug statements it uses 26 8E 97 34 2D 40 55 0F 6A 76 D9 03 64 8D 1C 17 1F 12 AF E2 as the fingerprint of the server SSL certificate. This is no longer valid as our hosting provider generated a new certificate on Wednesday, 6 June 2018 at 01:11:43 CET. Each cert is only valid for 3 months.

Current versions of the ESPaper client don't check the cert's fingerprint but validate the certificate chain which is much more stable over time.
commented by (180 points)
I've downloaded the version on Github : https://github.com/ThingPulse/espaper-client
Is this the latest?
commented by (8.8k points)
You are right. The code using the root certificates has not been published yet (still sitting on my laptop), but we'll do this as soon as possible, hopefully tonight. As  a quick fix you can update line 82 (https://github.com/ThingPulse/espaper-client/blob/master/settings.h#L82) with this new finger print "3E 12 02 6B BE 41 EF A7 29 8C 1F 2C 25 3C 6D 21 7C 6C 83 37". As Marcel mentioned, this would only be a quick fix since in three months you'd have to change the finger print again. The upcoming code using the root certificates will not require you to change the finger prints anymore. I'm sorry for the inconvenience!
commented by (180 points)
It work! Thank you so much!
commented by (8.8k points)
I just updated the espaper-client code. It now uses the root certificate which should work much longer than just three months. I suggest you update your code to our latest revision on github to avoid connection problems. I also improved logging a bit, so a WiFi connection issue will be displayed differently now on the screen.

Welcome to ThingPulse Q&A, where you can ask questions and receive answers from other members of the community.

https://thingpulse.com

...