-
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
ADSBHub sometimes key could not work #150
Comments
Hi, I'll see what we can do to escape special chars, it's always a burden to plays with that kind of issue. About docker image tag, sorry I won't explain that in the doc, this is very basic docker stuff and you should rather get familiar on how docker tags are working on their doc. |
Did you try to pass the environment variable with simple quote?
If you don't, bash/zsh etc. will substitute the $xxx with the variable value. |
In fact i was tried simple quote few days back, because had space in some env, but now i did just copy/paste, so no. As i don't want to open another issue is it will be good to mention here my observation on message rate of dump1090 WebUI? Saw more than twice increased rate, after enabling Radarbox, no matter with or without MLAT. Ususally i have 500msg/s in both dump1090 and tar1090, wich is fed by dump1090, but now when i start Radarbox feeding, at same conditions i get 1300mes/s and this is only in dump1090. On tar1090 and graph1090 rate is my normal 500mes/s. What can cause this and what i could do to fix it or diagnose it, as looking on the logs dosn't help me alot on that. |
I'm sorry I won't be any help on that. |
I had an issue with feeding ADSBhub. First i realise that just removing the container and starting with new env vars doesn't update the image, so please add in the manual :latest as here:
Next problem was that mine generated key contains that part:
1.
.........o88{xA94knz$aRSGnjU+{f3;~3J8$WHM).........
2.
.........o88{xA94knz+{f3;~3J8).........
After checking the real content of env vars with
docker exec -it <container_name> env
it was as on 2.So it always good to check if your key contains "$", just add new station in ADSBhub and delete that one.
The text was updated successfully, but these errors were encountered: