@MartinHBramwell Well i installed successfully following the guide here. Go to /etc/nginx/sites-available and delete the file named default. Install the Werkzeug version recommended and reboot the server. Your install should come online.
You can ignore sudo ln -s pwd /config/nginx.conf /etc/nginx/conf.d/frappe-bench.conf as it doesn’t seem to work. Just got to /etc/nginx/sites-available and delete the file “default” instead and follow the other steps as outlined. Once you’re done, reboot the server and you’ll be able to login to your install.
CAUTION: DO NOT run apt-get update and apt-get upgrade before installing. there’s a new dependency that bench doesn’t support yet so your installation will break if you update before installing.
If that’s the root cause of what I’m seeing I’m gonna slash my wrists!!! It would mean I’ve spent the most of last month tracking down 3rd party bugs that land at just the exact moment I finish making a complex change. Two days making changes. A week tracking down why it won’t work. Gah!
@MartinHBramwell Well I was too much in a hurry trying to get my instance to work that I didn’t note the name of the dependency. It’s essentially an upgrade that is explicitly mentioned will break bench because it’s not supported yet. And true to the warning bench broke after the install. I’ll try and recreate the error later if I can and report here.
Seems like the recent install issues were faced due to all requirements not being pinned in version-12 as of right now. We have already merged this PR in the version-12-hotfix branch and this issue will be fixed in the coming release.