-
Notifications
You must be signed in to change notification settings - Fork 54
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
WizardInternetBackendError or InternetBackendError #38
Comments
Yes. It means our server couldn't be reached. Do you have Internet Could you possibly send me a Wireshark capture of the network traffic? Den 19 okt. 2016 6:43 em skrev "eaandersen" notifications@github.com:
|
Thank you for the reply. I have an internet connection on the device. I connect to the RPi remotely without issue and there's no issues connecting to external repositories (i.e. node, python). The device is connected to a corporate network and it is possible that traffic is blocked by a firewall. Is there a mechanism to add a client without connecting to the Flic server? |
Do you know if dns requests are blocked on your network? Such are made to a Anyway, could you try an earlier release? There the requests are made a bit Den 19 okt. 2016 7:38 em skrev "eaandersen" notifications@github.com:
|
Can you please specify the name(s) of the public DNS servers and the flic server name? I will test it out using host or dig from the terminal As for the earlier release, which one do you recommend? beta v0.1? |
The used servers are 208.67.222.222, 8.8.8.8 and 209.244.0.3. The host "api.flic.io" is the one to be resolved. You can test beta v0.1. It doesn't have the scan wizard so you have to simply start scan manually and then connect manually when you see it advertises in public mode. |
I have exactly the same problem. First button was verified, but I'm not able to verify more buttons, always getting WizardInternetBackendError. I captured the traffic using Wireshark and two bridged network interfaces on my Windows PC where Wireshark is installed (one interface connected to my RPI, the other one to my router). Just sent the *.pcapng file to flic@shortcutlabs.com Pinging api.flic.io from my RPI:
|
Remark: I'm not connected to a corporate network or stuff like that, just using a normal router from my ISP. No firewalll for outgoing traffic configured. |
Remark 2: Unlikely that 2 people experiencing this issue at exactly the same time even if the current version is released since July, isn't it? Maybe something is wrong with the verificaton server? |
I checked your wireshark capture and everything looked fine there... |
Thank you! Output of simpleclient:
Output of flicd:
|
Could you try this: https://drive.google.com/open?id=0B-kW5rSvtUYnb29hNkpUT0xEaGs on your Raspberry Pi? |
Hi, |
Right.. try this one :) |
I don't know why, but with this version it works fine! After I successfully added a second button, I switched back to the original flicd version to be sure and tried to connect a third button -> error message appears. Switching back to your patched version and trying to connect the third button again -> works fine. I always used the same sqlite db for everything. Log of a verify process on the patched version which worked fine:
|
That's strange... There is nothing different among them at all except the logging. Maybe you could try a few other times? |
Ah, now I could reproduce the error with the version with logging (tried to connect again with a new db):
|
I used the original beta version (v.0.1) to test multiple devices and it worked fine. All of the devices were successfully registered in the sqlite database. To test out the newer release, I copied the sqlite database pre-populated from v0.1 to the folder with the latest release and all 4 buttons work nicely. You may want to patch v.0.3 with networking methods included in the original version. As a workaround, I'm ok to use v0.1 to populate new devices in the database and move it to the newer release folder. |
Ahaaa, found the bug. |
Works great, successfully tested 5 button verifications 2 times 👍 |
Thank you for the update. Are you planning to push the changes to Github? Or do you prefer we use the file uploaded to Google Drive? |
Yes I'll update the github repo as soon I get time. Den 24 okt. 2016 8:15 em skrev "eaandersen" notifications@github.com:
|
I'm having this same issue, but then on a regular Ubuntu system. When will a binary for this be available? |
@idserda I just created a new release. Could you try that one? |
@Emill just for the feedback, I'm currently working with the new release and it works perfectly! Thanks. |
I am having this issue also from the newest github verison. How do I resolve? |
This is an already fixed issue. Exactly what issues do you have? |
When I try to connect I get the following error (RPI 4, running 32bit Raspbian): startScanWizard |
Have you managed to connect the button to an Android or iOS device successfully? |
I have paired the buttons many times before - always with ease. I do also have all the button adresses written down - am I able to use those to connect without the ScanWizcard? |
Yes, but that won't make any difference. ScanWizard is simply a utility that performs scan and then connects. |
Bluetooth monitor ver 5.50 |
What am I looking for in Wireshark (rather than posting the entire log, which is huge) |
Update: I have just tried installing a fresh Rasbian on a Pi Zero W and I keep getting the same error. |
I have the same issue I think on a RPI 4 with hassio; the flicd output is:
I can't seem to ping api.flic.io either but it answers on http |
@Cyriuz Do you use the latest published flicd here? |
I also consistently keep getting the WizardInternetBackendError when attempting to connect the button to RaspberryPi Zero. The button connects fine to a phone. I made sure to remove it from the phone before attempting to connect it to the RaspberryPi. |
ping api.flic.io doesn't work, perhaps by design. wget https://api.flic.io/ping returns --2020-05-31 15:45:26-- https://api.flic.io/ping curl https://api.flic.io/ping returns correctly: {"success":true} |
@Emill Using latest from here yes. Both wget and curl work fine for me for api.flic.io, even inspecting the cert everything looks fine. Can I somehow get more info from flicd which certificate it has a problem with? |
For some reason the web server chose to send an expired intermediate certificate that affects some TLS clients. It should be fixed now so could you please try again? |
Thx - It is working now! |
Yes, it works now, thank you! |
Nice! and sorry for the inconvenience... |
Thanks. It works now. |
I've attempted to pair/register more than one client to the same bluetooth controller and always receive the "InternetBackendError" error message. Can you please explain the error code?
The text was updated successfully, but these errors were encountered: