As Discourse is not using Apache how to password protect e.g. a staging environment (Digital Ocean droplet with Discourse docker) as you would do with .htaccess (Apache)?

There is no apache, but NGINX is running inside the Discourse container. This topic may help: [image] Persistent nginx/discourse.conf? Self-hosting If anyone else is looking to add auth_basic to their site during development, and make it persistent across ./launcher rebuild app just update your containers/app.yml with: ## Any custom commands to run after building run: - exec: echo "Beginning of custom commands" - replace: filename: "/etc/nginx/conf.d/discourse.conf" from: "# auth_basic on" to: "auth_basic on" - replace: filename: "/etc/nginx/conf.d/discourse.conf" from: "# auth_basic_user_file /etc/nginx/htpa…

Perfect, thanks @david :innocent:

Just added it but now every picture from https://cdn-uploads.example.com and https://cdn-origin.example.com requires to enter the auth password. Is there a way to only protect https://discourse.example.com? Otherwise I get this now: [image]

I’m not sure exactly how to achieve that, but maybe someone else will jump in if they have some ideas. It should be possible with some tweaks to the nginx config. As a workaround, and since this is a staging server, could you just disable the CDN? If you use the same domain for assets, they will automatically be sent the authentication header so you won’t need to enter the auth password again.

Yes sure, if that is the recommended approach for a staging environment if you use S3 buckets for backups and uploads as well as CloudFront as CDN for uploads and origin on production. No need to really have all of that for a staging environment?

DISCOURSE_USE_S3: true DISCOURSE_S3_REGION: us-east-1 DISCOURSE_S3_ACCESS_KEY_ID: XXXXXXXXXXXXXXXXXXXXXX DISCOURSE_S3_SECRET_ACCESS_KEY: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX DISCOURSE_S3_CDN_URL: https://cdn-uploads.example.com DISCOURSE_S3_BUCKET: example-uploads DISCOURSE_S3_BACKUP_BUCKET: example-backup DISCOURSE_BACKUP_LOCATION: s3 DISCOURSE_CDN_URL: https://cdn-origin.example.com And the main domain for staging is currently https://staging.example.com Still, I am auth prompted for every single request from cnd-origin with the proposed code when accessing https://staging.example.com

Update for those running into the same issue: All distribution settings reference - Amazon CloudFront The values that you specify when creating or updating a CloudFront distribution, such as origin and cache behavior settings. We had to whitelist the Authorization headers in Cloudfront for cdn-origin. It’s seem I was not prompted for auth for cdn-uploads. Works now.

I turn on login required on the staging site. You can do it with an environment variable in the app.yml so that it’s persistent.

No good enough if Google or anybody else is finding the site. Anyways works now.

How to password protect staging environment?

Product Support Self-hosting

david (David Taylor) August 21, 2020, 10:44am 7

This nginx change certainly shouldn’t affect S3 uploads or the S3 CDN. NGINX is not involved there at all. I had assumed you were using local uploads with a CDN?

The ideal situation is to make the staging site configured identically to the production site.

Topic		Replies	Views
Restrict access to your Discourse site with HTTP Basic Authentication Sysadmins how-to	0	2242	October 23, 2020
Installing Discourse Behind Reverse Proxy using recommended (supported) installation Self-hosting	7	4380	May 6, 2026
Setup Nginx as a reverse proxy for discourse forum without dockers &any containers Development	1	713	August 17, 2022
Discourse with Cloudflare and Digital Ocean Self-hosting nginx	2	489	August 5, 2024
Discourse with jwilder/nginx-proxy howtos? Self-hosting	11	8498	April 6, 2019

How to password protect staging environment?

Related topics