Conversation

Notices

1. Embed this notice
   Dude Named PhoneBoy [TN] (phoneboy@noagendasocial.com)'s status on Wednesday, 14-Dec-2022 03:05:25 JST Dude Named PhoneBoy [TN]

   • Matt Hamilton [Maryland]

   Hey @eriner did you whack the “fe” version of the UI for No Agenda Social or do you need to jiggle the handle on it?

   • Embed this notice
     Matt Hamilton [Maryland] (eriner@noagendasocial.com)'s status on Wednesday, 14-Dec-2022 03:05:24 JST Matt Hamilton [Maryland]

     in reply to

     • Alex Gleason

     @PhoneBoy Huh. All of the proxied requests are returning an HTTP 526 error.

     Maybe @alex can clue me in as to what is going wrong here? The FE is delivered as static content only, so I don't have any server-side logs to go off of. I've tried updating Soapbox, restarting nginx to force cache clear, and clearing cache in my browser.

   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Wednesday, 14-Dec-2022 03:05:24 JST Alex Gleason

     in reply to

     • Matt Hamilton [Maryland]

     @eriner @PhoneBoy I guess you have your nginx pointing fe.* through to Mastodon, and the api ain’t working: https://fe.noagendasocial.com/api/v1/instance

     That’s something that needs to be fixed on the nginx side.

     (If you’re feeling brave enough to do a custom build, you could also compile it like NODE_ENV="production" BACKEND_URL="https://noagendasocial.com" yarn build and it would hardcode the URL in the build, pointing all API requests to the main site.)

   • Embed this notice
     Matt Hamilton [Maryland] (eriner@noagendasocial.com)'s status on Wednesday, 14-Dec-2022 03:09:00 JST Matt Hamilton [Maryland]

     in reply to

     • Alex Gleason

     @alex It seems to be working fine if the session is authenticated. On the browser I'm posting this from, I can load it fine just fine because I'm authed already. Non authenticated browsers return 526.

     Nothing about the nginx or server configuration has changed in a long while, at least unless it's become sentient and is doing stuff on its own.

   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Wednesday, 14-Dec-2022 03:09:00 JST Alex Gleason

     in reply to

     • Matt Hamilton [Maryland]

     @eriner Maybe Mastodon changed.

     But… the error page is not from Mastodon.

     Unless maybe Mastodon is sending a 526 with no body and nginx is showing the custom error page?

     What even is a 526 anyway?

   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Wednesday, 14-Dec-2022 03:09:26 JST Alex Gleason

     in reply to

     • Alex Gleason
     • Matt Hamilton [Maryland]

     @eriner Oh. https://bobcares.com/blog/how-to-fix-cloudflare-error-526-invalid-ssl-certificate/

     You have an expired cert in Cloudflare?

   • Embed this notice
     Matt Hamilton [Maryland] (eriner@noagendasocial.com)'s status on Wednesday, 14-Dec-2022 03:26:00 JST Matt Hamilton [Maryland]

     in reply to

     • Alex Gleason

     @alex well that's embarrassing...

   • Embed this notice
     Matt Hamilton [Maryland] (eriner@noagendasocial.com)'s status on Wednesday, 14-Dec-2022 03:26:00 JST Matt Hamilton [Maryland]

     in reply to

     • Alex Gleason

     @alex @PhoneBoy all fixed now. I had forgotten to add the fe subdomain to the autorenew list and the custom 500 error page obscured the cert expiry error. Thanks @alex, sorry to bother you. I swear I'm not always this retarded.

     Alex Gleason likes this.
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Wednesday, 14-Dec-2022 03:26:20 JST Alex Gleason

     in reply to

     • Matt Hamilton [Maryland]
     @eriner @PhoneBoy >I'm not always this retarded.
     
     Fortunately, I am.