When I try to activate Data Collection and enter my email address, it gives me the error message “An error occured when checking the registration: Failed to query the server.” This happened after the upgrade to 3.9 and 3.9.1.
If you already had data collection activated in the previous version, read on. Just a workaround. In the 3.9 version, I checked out the data collection to uninstall Haas. And then I tried to log in again and I got the same error. So I did schnapps rollback to the previous snapshot: https://doc.turris.cz/doc/en/howto/schnapps and waited again for update on 3.9. And that’s it. I’ve seen this bug somewhere here, I think the team knows about it. I just can’t find it. (I think it was a screenshot).
Schnapps is worth trying, but it’s up to you. I don 't think it’s necessary. I just ran the 3.9.1 update. As somebody from the team wrote somewhere haas will need some further work. So we have to wait a few weeks. I’m still looking there once a month. So I look forward to the next update.
I just completely reinstalled my Turris 1.0 today (reflash to 3.6.5, update to 3.9.1) then migration to btrfs and I am facing same issue while trying to setup Data Collection again.
EDIT: In meantime, I had disconnected cable from WAN and connected it again. Data Collection now shows as working. There was no need to enter email again, after failed attempts.
I got an email that Data Collection still doesnt work. While it was showing as configured in Foris before, after refreshing the page for a few times, it shows as not configured now. After providing email address, same error is shown as before. (Failed to query the server)
Registration working now after several hours waiting and restart yesterday (restart did not solve it in first hand). Maybe a update of packages (opkg update) solved it.
Please don’t revive thread, which are year and half old. There was a temporary outage in whole DC 1 in CRa Tower, which affected some of our services. Now, it should be up and running.
But the issues not being able to setup Data Collection with fresh new medkit happend during weekend. And exactly the approach above creating the file manually helped immediately.
So I think this is exactly the correct thread to continue cause the issues is still in place even after half a year
I guess the script is not triggered after new fresh medkit introduction.