I had to remove the force https function on the site to allow for alternate access. As soon as I did that all logos became broken. The logos cant load because they are being uploaded as http not https. Regular images in the posts seem fine. Its just the logos.
AI-generated summary
The discussion revolves around issues with loading HTTP images over Tor on a Discourse site. Garrick initially disabled the “force https” function to allow for alternate access, but this resulted in broken logos uploaded as HTTP. dax inquired about the type of access Garrick needed to disable the setting, and Garrick explained it was necessary to access the site from a Tor address.
hellekin suggested that using TLS over Tor might be unnecessary, as Tor Hidden Services are already encrypted. However, if the site has a DNS-visible domain, a possible solution could be adding a Subject Alternate Name to the SSL certificate. Since LetsEncrypt doesn’t support this yet, an alternative approach could be using the // shortcut or path_only to determine the full URL based on the host scheme.
What kind of access did you need to have to disable the Force HTTPS setting from the site?
It was blocking my login access from a tor address. Even if the torrc file was changed to port 443.
Using TLS over Tor is indeed overkill (since Tor Hidden Services are already encrypted) but if your site has a DNS-visible domain, you should be able to add a Subject Alternate Name that matches .onion in your SSL certificate – except that LetsEncrypt does not support it yet.
If indeed you have both HTTPS and HTTP+Tor, it’s a bit of a problem. Maybe instead of force_https, Discourse could use the shortcut // like for assets, or use path_only so that the full URL is determined by the host, and thus always match the calling scheme.