Option to not require HTTPS (Tor-Only Access) #200

Open
opened 2021-08-09 00:08:03 +00:00 by mindofjoe · 0 comments
Member

Pleroma maintains a guide for running a Tor-only instance (link). The guide runs users through configuration for HTTP-only access, since conventional wisdom says (1) Tor's encryption and methodology are sufficient and (2) dealing with SSL certificates for onion addresses is tedious at best. Pleroma's Tor guide gives instruction to force the instance's scheme to HTTP as well as disabling CSP.

Unfortunately, when attempting to use AdminFE for administration, it seems AdminFE is requiring HTTPS.

Instructions to disable the requirement in AdminFE or additional instructions in Pleroma's Tor guide to deal with the requirement (additional nginx server blocks for port 443 listening & self-signed certs, maybe?) would help make the user experience seamless.

Pleroma maintains a guide for running a Tor-only instance ([link](https://docs.pleroma.social/backend/configuration/onion_federation/)). The guide runs users through configuration for HTTP-only access, since conventional wisdom says (1) Tor's encryption and methodology are sufficient and (2) dealing with SSL certificates for onion addresses is tedious at best. Pleroma's Tor guide gives instruction to force the instance's scheme to HTTP as well as disabling CSP. Unfortunately, when attempting to use AdminFE for administration, it seems AdminFE is requiring HTTPS. Instructions to disable the requirement in AdminFE or additional instructions in Pleroma's Tor guide to deal with the requirement (additional nginx server blocks for port 443 listening & self-signed certs, maybe?) would help make the user experience seamless.
Sign in to join this conversation.
No labels
blocked
stale
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pleroma/admin-fe#200
No description provided.