Spyke

Syndicated from the fediverse. Read and engage on the original instance.

View original on infosec.pub

1 reply

I had this when the reverse proxy configuration wasn't correct. You need to ensure the correct paths, methods and headers are routing correctly to the lemmy instance as opposed to the lemmy-ui instance -- as per the documentation.

2

You reached the end