Hello,
I need some help with ssl.https. Friday I change my ISP and now the scripts that we have with ssl.https (API to solcast, esios.ree.es, tomorrow.io...) don't work.
I tried the url directly on a Internet browser, and it works. But not from SpaceLynk. I get the response: "Try again"
I don't think the new router or new ISP have anything to do with it, as the requests are resolved without any problem from a PC browser.
But after going round and round I'm lost, and I don't understand why all the requests have stopped responding.
Any ideas would be welcome
Thanks, and kind regards
I answer myself, the problem was DNS provider,
changing in SpaceLynk with the google 8.8.8.8, works. But not with my gateway (192.168.x.1) thats have Movistar DNS 80.58.61.250.
I'm curious why from a web browser it resolves the DNS with 80.58.61.250 and not from spacelynk.
I need some help with ssl.https. Friday I change my ISP and now the scripts that we have with ssl.https (API to solcast, esios.ree.es, tomorrow.io...) don't work.
I tried the url directly on a Internet browser, and it works. But not from SpaceLynk. I get the response: "Try again"
Code:
res, err = ssl.https.request(url)
log (res, err)
Code:
solcast 25.04.2022 17:07:39
* arg: 1
* nil
* arg: 2
* string: Try again
I don't think the new router or new ISP have anything to do with it, as the requests are resolved without any problem from a PC browser.
But after going round and round I'm lost, and I don't understand why all the requests have stopped responding.
Any ideas would be welcome
Thanks, and kind regards
I answer myself, the problem was DNS provider,
changing in SpaceLynk with the google 8.8.8.8, works. But not with my gateway (192.168.x.1) thats have Movistar DNS 80.58.61.250.
I'm curious why from a web browser it resolves the DNS with 80.58.61.250 and not from spacelynk.