-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update rmfakecloudctl to support dev server #607
base: testing
Are you sure you want to change the base?
Conversation
Any logs on the server side when this loop occurs? |
The second image is the server side logs, it just loops through that. |
also adding dev.tectonic.remarkable.com and dev.internal.cloud.remarkable.com to the /etc/hosts and CA cert seems to make it function properly. |
#932 would add full support |
@StarNumber12046 I've merged your changes, but you mentioned that there are still issues with it? |
It seems like, in some cases (only once for about a minute today), it got stuck on periodically refreshing the decicetoken because of dev.ping.remarkable.com/v2/events (which is not exactly part of the cloud) |
That should still be part of rmfakecloud. I would recommend opening an issue on that repository to get it resolved. |
If you have
ServiceEnvironment
set toDev
, the current rmfakecloud-proxy configuration generated by rmfakecloudctl will not work. You'll need to addwebapp-legacy-dev.cloud.remarkable.engineering
to the proxy list.