-
Notifications
You must be signed in to change notification settings - Fork 60
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
rmfakecloudctl: set-upstream does not validate that URL is valid #796
Comments
What does |
Another thing I just took a peek at was my
|
The device token is unrelated to if the proxy is able to run or not. The issue you have right now is that the proxy isn't running, so the device isn't able to communicate with your rmfakecloud instance. What happens if you try to run |
Got it. Here's the output.
|
Oh, you should set your upstream address to be a valid url. I assume it should be |
Oh my goodness. That's it. Thanks. 🤦♂️ |
No worries, this does show that rmfakecloudctl should do a tiny bit of validation on the URL provided and give a bit of insight into why it isn't valid if you miss something it expects. |
Describe the issue
Upon installation status is listed as
Status: enabled (failed)
on RM1To Reproduce
Steps to reproduce the behaviour:
Expected behaviour
I expected the status to be
enabled (active)
Screenshots
Device information (please complete the following information):
Additional context
Installing on two RM1s. The first installation went swimmingly and is working just fine, but I get a
Status: enabled (failed)
on the second RM1 device. My server is also playing nicely with an RM2.Looking in
log.txt
I see an error about not having a device tokenI'm not sure what to do. I've tried reinstalling (I'm on 2.15.1.1189) and like I said the install worked well on the other RM1. Any suggestions on where to look?
The text was updated successfully, but these errors were encountered: