Didn’t you do some custom stuff to your nginx file…?
I am not getting this and I did a fresh install so it’s not a normal troubleshooting help when the user customizes / edits the container files etc and gets errors.
Also, you most likely did not rebuild your containers, you probably just ran the normal upgrade containers which does not contain the build parameter which will force a rebuild of all containers with all updated info…
I was trying to type it manually because initially auto-completing it was booting me out, like I showed in the GIF, so I thought maybe my tabbing was causing it.
You can disregard this post if following your advice from a previous post now nullifies my eligibility for support. I’m considering paid Screenly; OSE is too unstable lately.
Anthias is all volunteer and community support, so what I meant was that it is hard to troubleshoot / help users that customize their units because I or if someone else helps, can’t keep track of what changes you’ve made, even if we suggest those changes, and if we suggest changes they are usually to fix something specifically for you, not for the Anthias system itself, otherwise that would be in the GitHub Issues and repo as a PR fix.
Basically, you have an issue after doing the upgrade from within a system that was already running, I would suggest doing a complete reinstall but instead of doing a whole flashing the SD card steps and doing all those previous steps, you simply completely delete your docker images/containers.
To do so, you would need to run the following commands:
stop and remove all containers:
========================
sudo docker stop $(sudo docker ps -a -q) && sudo docker rm $(sudo docker ps -a -q)
remove all docker images and docker data:
==================================
sudo docker rmi $(sudo docker images -a -q) && sudo docker system prune -a
Then, you can run the bash install script and I would simply suggest pressing yes to running the upgrade so that packages are updated.
This creates all containers again using the latest master repo but beware that during this Python3 migration there are some errors here and there, thus if you can try to fix the nginx error for now, that would be better since we dont know how many other things are broken during Py3 migration besides the ones reported by users and ones we find ourselves.