Help! Flask with Flask_Login on Apache2

[@d2xdt2]

It sounds like a file system permission issue. Have you tried the same with eg Digital Ocean? It could also be app armour that is preventing certain actions. I don't think it have anything to do with remote/local, but rather the OS and how it is configured and which services that are running. Have you looked at the logs for Apache and AppArmour that they say on the remote? To avoid this issue, run and deploy it in a Docker/Podman container.

[@stryker2k2]

That is a lot to think of! Thank you for highlighting those options! I have 'fixed it'... but fixed it with a bandaid. That bandaid is to strip out the Flask Login library and go straight with Python Sessions. I'd love to actually go back and try the Flask Login library again on a different hosting platform. In this video, I was using Linode and Apache2. This was my first time troubleshooting an Apache2 server. It usually works out of the box. So, I "looked" at the logs but my eyes weren't trained enough to understand it... or even properly push to the logs to be read later.