You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey,
I had an bad issue, that federation wasn't possible anymore. Logs where showing likely "server key is invalid or corrupt" and request thats ended in a 404 to my partners server .well-known route.
Federation tester was still saying thats all okay on both servers. Turns out it was an tailing slash at the end of my proxy_pass on my nginx server config, that doesnt belong there:
Sadly that happend on a migration from apache. Maybe its possible to check and recognize a misconfiguration like this one. A false-positive check result makes debugging hard.
73
The text was updated successfully, but these errors were encountered:
Hey,
I had an bad issue, that federation wasn't possible anymore. Logs where showing likely "server key is invalid or corrupt" and request thats ended in a 404 to my partners server .well-known route.
Federation tester was still saying thats all okay on both servers. Turns out it was an tailing slash at the end of my proxy_pass on my nginx server config, that doesnt belong there:
wrong: proxy_pass http://localhost:8008/;
right: proxy_pass http://localhost:8008;
Sadly that happend on a migration from apache. Maybe its possible to check and recognize a misconfiguration like this one. A false-positive check result makes debugging hard.
73
The text was updated successfully, but these errors were encountered: