Conversation

Notices

1. Embed this notice
   Alex Gleason (alex@gleasonator.com)'s status on Sunday, 20-Aug-2023 00:32:17 JST Alex Gleason

   • Back to the Alan
   • burner
   @alan @burner CSP is a header in the HTTP response called "content-security-policy"
   
   You can see it by running: curl -I https://blimey.social
   
   Run: curl -I https://gleasonator.com
   
   Compare the content-security-policy header.
   
   You will see the "style" section is different. Mine allows unsafe-inline, yours allows only a single nonce
   
   You need to make it return the correct thing. You can also check the console logs in the browser to see the errors resulting from this.
   
   Paste your Nginx file into ChatGPT and ask how to do it.
   
   I don't want to write up specific instructions on this because I don't want to encourage other people to do it. It's not a good thing. Akkoma has broken support for other frontends. This is an Akkoma problem.
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Sunday, 20-Aug-2023 00:36:59 JST Alex Gleason

     in reply to

     • Back to the Alan
     • burner
     @alan @burner Did you see my reply to them? They are not using Soapbox as the main frontend. This is what I mean by "Soapbox supports Akkoma, but Akkoma does not support Soapbox." In their custom setup the are running Soapbox atop Akkoma with a custom Nginx to control headers and routing. They have made it work with a custom setup. The default setup is the opposite, where Akkoma is in front and Soapbox is served through it, so Akkoma controls it.
     
     There is no easy way out of this. You're going to have to read up and learn how this all works.
   • Embed this notice
     Back to the Alan (alan@blimey.social)'s status on Sunday, 20-Aug-2023 00:37:08 JST Back to the Alan

     in reply to

     • burner

     I appreciate that, thanks for the advice.

     Do you think this is fixable without creating a fork, given that someone else is running Soapbox with up to date Akkoma?

   • Embed this notice
     Back to the Alan (alan@blimey.social)'s status on Sunday, 20-Aug-2023 00:43:59 JST Back to the Alan

     in reply to

     • burner

     Ah, I thought you were telling me that I wasn’t using Soapbox as my main frontend.

     I’ll get researching this, then.

     Thanks again for your help 👍🏻

     Alex Gleason likes this.
   • Embed this notice
     burner (burner@norwoodzero.net)'s status on Sunday, 20-Aug-2023 00:54:51 JST burner

     in reply to

     • Back to the Alan
     • verita84 :Debian_logo: :firefox: :bing: :android:
     @alan @alex the guy who helped me set soapbox up is @verita84, not sure how he did it.
     Alex Gleason repeated this.
   • Embed this notice
     verita84 :Debian_logo: :firefox: :bing: :android: (verita84@poster.place)'s status on Sunday, 20-Aug-2023 00:54:51 JST verita84 :Debian_logo: :firefox: :bing: :android:

     in reply to

     • Back to the Alan
     • burner
     @burner @alan @alex
     
     We had to use a subdomain
     I could not get soapbox to work at all to replace PleromaFE on akkoma. Tried many things