-
Notifications
You must be signed in to change notification settings - Fork 17
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
403 Forbidden when clicking monitored aircraft Alert List #210
Comments
I believe it takes a little while for it to sort itself out after being deployed, probably needs a plane present in the plane-alert-db.txt database to show up first. That could take a bit, maybe hours or a day or two depending on how high traffic your area is. Just keep trying, it should start to work |
It's NOT the plane-alert-db.txt that's the issue, it's working fine - it's when built in "alertlist.txt" - ie. the list of used for Plane-Alert. |
Sorry - Yes off course it's the plane-alert-db.txt - the file is there and can be read - suspect it's something to do with the web server not being able to read the file and/or not allowed to follow symbolic links... I just can't figure it out... |
In a newly deployed planefence container - when I click on the monitored aircraft Alert List - I get a 403 Forbidden.
Looking at the link via the page http://:8088/plane-alert/ - I can see it points to http://:8088/plane-alert/alertlist.txt
Looking inside the planefence container, I get:
Both files can be read from within the planefence container:
I'm also a little confused as to why there are 2 different files?
The text was updated successfully, but these errors were encountered: