Skip to main content

I get this for a day now, something amiss @rolle ?
@Roni Laukkarinen
in reply to Harald Hannelius :verified:

Roni Laukkarinen
Roni Laukkarinen
• •
Hmm, interesting. Which client?
in reply to Roni Laukkarinen

Roni Laukkarinen
Roni Laukkarinen
• •
The API works fine https://mementomori.social/nodeinfo/2.0
in reply to Roni Laukkarinen

Roni Laukkarinen
Roni Laukkarinen
• •
I recently added a cert and rewrite for www.mementomori.social but that should not affect anything. You should send feedback for that app developer.
in reply to Roni Laukkarinen

Nicd
Nicd
• •
Looks like this should be mapped by Mastodon but it's returning 404 on mementomori.social: https://docs.joinmastodon.org/dev/routes/#nodeinfo

Routes

How HTTP methods map to controllers and actions.
docs.joinmastodon.org
in reply to Nicd

Roni Laukkarinen
Roni Laukkarinen
• •

@nicd I have default allow alls for .well-known just like here https://github.com/mastodon/mastodon/blob/main/dist/nginx.conf

Is something else needed?
I really think this is a client issue as API works fine. https://mementomori.social/nodeinfo/2.0

@harald


mastodon/dist/nginx.conf at main · mastodon/mastodon

Your self-hosted, globally interconnected microblogging community - mastodon/mastodon
GitHub
@Harald Hannelius :verified: @Nicd
in reply to Roni Laukkarinen

Jarno
Jarno
• •

@nicd .well-known/nodeinfo returns 404 for me too. Also the webfinger endpoint. For comparison, mastodon.social responds to these with 200 + the associated JSON.

I didn't notice any ActivityPub .well-known endpoints in the config @rolle linked, only for the certbot challenge. I think others would fall under the default "location /" block.

Perhaps add blocks for the endpoints listed here: https://docs.joinmastodon.org/dev/routes/#well-known to NGINX config? Something like

location /.well-known/(nodeinfo|webfinger|...) {
proxy_pass http://backend$request_uri;
}

404 for mementomori.social well-known
200 + JSON (truncated) for mastodon.social

Routes

How HTTP methods map to controllers and actions.
docs.joinmastodon.org
@Roni Laukkarinen @Nicd

Roni Laukkarinen reshared this.

in reply to Jarno

Roni Laukkarinen
Roni Laukkarinen
• •

@oranki

It is really strange these nginx blocks are not in the official docs. Why?

It doesn't work with that simple location block example you have. Any idea on what to add in the location block?

Does @renchap have any information about this?

@nicd @harald

#MastoAdmin

#mastoadmin @Renaud Chaput @Jarno @Harald Hannelius :verified: @Nicd
in reply to Roni Laukkarinen

Jarno
Jarno
• •

@renchap

I missed the end of the line
try_files $uri (at)proxy

So that extra location block shouldn't be necessary, sorry about that. Maybe a regression in Mastodon, since MementoMori runs bleeding edge versions?

@Renaud Chaput
in reply to Roni Laukkarinen

Roni Laukkarinen
Roni Laukkarinen
• •

@oranki @renchap @nicd
Hmm okay, wrong alarm, I had a mistake in one of the location blocks.

Seems to work now with the default nginx conf. No extra location blocks needed.

https://mementomori.social/.well-known/nodeinfo

@Renaud Chaput @Jarno @Nicd
in reply to Roni Laukkarinen

Pachli
Pachli
• •

@nicd You're checking the wrong URL there, #Pachli starts at the /.well-known/nodeinfo endpoint and reads that to get the URL for the actual nodeinfo file.

Pachli uses this information to figure out what type and version of server it's talking to, in order to enable/disable functionality.

#pachli @Nicd
in reply to Pachli

Roni Laukkarinen
Roni Laukkarinen
• •

@pachli

Yeah, it appeared that my location blocks were wrong in nginx conf, perhaps happened during yesterday's change when I updated the SSL certs for redirecting domains (.well-known location block had a mistake).

It works again here too: https://mementomori.social/.well-known/nodeinfo

@nicd @harald

@Harald Hannelius :verified: @Pachli @Nicd
⇧