Mike McCready

@nagash77 - Thank you very much for confirming you do not backport fixes to older versions of Cypress. I was guessing this was the case, but I was a little...

@nbouvrette Could you say which OS you are testing on? `localhost` can work differently depending on this. I didn't find any workflows on https://github.com/Avansai/next-multilingual (.github/workflows) to give me a hint.

@nbouvrette > I'm on macOS 13.2.1 I was hoping to be able to try this out, however on https://github.com/actions/runner-images `macos-latest` is equivalent to [macos-12](https://github.com/actions/runner-images/blob/main/images/macos/macos-12-Readme.md) so your version is not yet...

@sushil-truemark > I temporarily resolved this issue by downgrading node version to 16.xx from 18.xx. Node.js `16` will enter [end-of-life](https://github.com/nodejs/release#release-schedule) later this year, so it may be better to look...

@fontcoderrrrrrr > I solved the problem by substituting http:127.0.0.1:yourport for http://localhost:yourport/. - This is the workaround described in https://github.com/jeffbski/wait-on/issues/137

Since this hasn't been picked up and the project I'm working on which was using Panini is closing down, I'm closing this stale issue.

@csvan / @DmytroKhomychPrintify I only see this error message in CI and this is where Cypress uses `Xvfb` (X virtual framebuffer) in place of a physical graphic hardware adapter.

If it can be determined that the error message in this issue is harmless: > [266:1014/183729.600834:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.portal.Settings.Read: object_path= /org/freedesktop/portal/desktop: unknown error type: perhaps it could be...

Going by previous similar messages, the message > ERROR:object_proxy.cc(590) Failed to call method: org.freedesktop.portal.Settings.Read is probably **not** causing test failures, **HOWEVER** if your test is failing, then this may be...

@cimak > I was getting this exact error when running cypress under WSL2/win11. [Installing XServer on windows](https://stackoverflow.com/questions/61110603/how-to-set-up-working-x11-forwarding-on-wsl2) worked for me, I'm not sure if it is a final solution but...