@halcyon it seems that my installation on ynh cannot connect to my pleroma instance. You have an idea how to debug this?

@marcus I think that shouldn't be a bug of your Halcyon instance.I tried logging in with my private account and everything worked fine.If there's a connection problem between Halcyon and Pleroma,it won't let you login at all.I think your adblocker plugins could block the connections to your Pleroma instance.Login works through Halcyon but all requests after that are directly from the browser to Pleroma which could be detected wrong as thirdparty tracker.

@halcyon ah, thanks for the tip. I have had Adblocker active. Do you also use 3rd party cookies?

@marcus Mastodon sets a session cookie (which counts as third party because Halcyon is on another subdomain) but I'm not sure if Pleroma has this session cookie,too.If that gets blocked,that doesn't matter anyway because Halcyon gets a OAuth Token at login which is used to authenticate you at Pleroma so that the session cookie is ignored here.

@halcyon hmm in web developer mode of firefox I see something like this: Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf https://pleroma.nsupdate.info/api/v1/timelines/home?. (Grund: CORS-Kopfzeile 'Access-Control-Allow-Origin' stimmt nicht mit '*, *' überein).

@marcus Oh sorry,I just noticed that I've completely forgotten this message.The problem seems to come from your Pleroma instance.Please edit your nginx.conf and remove the Access-Control headers from it.They've been set by Pleroma itself for a few months and if these headers are duplicated (one time from Pleroma and one time from nginx),that will cause bugs with clients on third-party domains (other subdomains are enough for the bug to appear).

Sign in to participate in the conversation
W3C CSS Working Group Mastodon

Mastodon server for anyone interested in CSS or general web development