-
Notifications
You must be signed in to change notification settings - Fork 43
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
Reference Lines Not Appear #52
Comments
Hi, Thank you for your report! It seems likely that you started with an empty database. The reference line will only appear if the station in the path is known at the time the packet is received. Typically, stationary stations send a packet only once every 30 minutes or so. I recommend waiting about an hour and then checking to see if received packets have a reference line. I'll keep this issue open so you can confirm before I close it. |
Ok, that was unexpected. I've cleaned everything and rebuilt the docker images, but I can't reproduce your problem (neither this nor the other regarding missing symbols). How do you start everything? Are you using docker or are you doing it in a different way? |
I still use docker on a raspberry pi. I think the problem is from the SSL setting on the apache. |
I have now setup the latest version on several different servers (using docker containers directly and deployed using kubernetes). I have not seen this problem on any of my setups. Note that I am using the docker files provided in the repository. I would like to help you, but I need more information on how to reproduce it. |
I'm using Docker and serving through a Cloudflare tunnel. There was no problem with the old version, but I think the latest WebSocket has an issue displaying reference lines through Cloudflare. |
Hello OM, latest update not showing reference line like this
The text was updated successfully, but these errors were encountered: