We tested on Tor and it worked, but now we could replicate the issue with i2p. Some time ago we introduced a cookie that would force connections to be routed through https (with cryptography) instead of http, so I imagine this cookie was causing this error. Now we removed it. Can you check if now it’s working? We came to the conclusion that this cookie was not needed because we have other code that automatically route connections to https when that’s available.
I am using firefox and mullvad browser, it is happening in both. It was working fine about a month ago. Other Tor & I2P sites work.
We tested on Tor and it worked, but now we could replicate the issue with i2p. Some time ago we introduced a cookie that would force connections to be routed through https (with cryptography) instead of http, so I imagine this cookie was causing this error. Now we removed it. Can you check if now it’s working? We came to the conclusion that this cookie was not needed because we have other code that automatically route connections to https when that’s available.
It is now working, thank you!