I really appreciate you don't give up on me!
But I'm sorry to tell this morning suggestion failed. Too bad, the site is almost error free w/ force_https=true but the 403.
/opt/bitnami/apps/discourse/conf/httpd-app.conf this way, is it OK?
RequestHeader set X_FORWARDED_PROTO 'https' env=HTTPS
# SetEnvIf x-forwarded-proto https HTTPS=on
<IfVersion < 2.3 >
Allow from all
<IfVersion >= 2.3>
Require all granted
Then, if you are to reproduce my environment, I gave you all my notes in post #13 & #14 of this topic.
Be careful, some parts are tricky because I've followed your manual but also did corrections to this procedure as in the "Redirect to www" (commenting SSL in httpd-vhosts.conf) and as the last correction I did to "Force https at Apache level" (editing
/opt/bitnami/apps/discourse/conf/httpd-vhosts.conf , see post #14). So the force_https=true in discourse settings is the third code added to do the same thing in the procedure I followed...
To summarize, it is a Bitnami Discourse from the GCP Marketplace + akismet & ads plugins + google & twitter logins + force www & https + GTM. Not that fancy, but rocky install.
Also, I will open new topics for the side issues (dirty version & PWA errors) to keep this topic on the 403 issue.
Wish you have a nice day.