[Bug] Can't access UI when running in WSL2

[FrankEBailey]

RomM version Latest

Describe the bug I'm on Windows 10 running WSL2 and Docker Desktop. My docker compose file works fine, and ROMM appears to run fine, however when I try to access it in my browser I get

Expected behavior I expected to be able to access the web interface of ROMM

Desktop (please complete the following information):

• OS: Windows 10
• Browser: Firefox
• Version: 129.0.1

Additional context

romm-log.txt docker-compose.txt

[gantoine]

Can you post the container logs?

[FrankEBailey]

The log is romm-log.txt as above, thanks

romm-log.txt

[FrankEBailey]

Not sure if this helps (I changed my port to 8118 in the compose file):

/romm # netstat -tuln
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       
tcp        0      0 127.0.0.11:38473        0.0.0.0:*               LISTEN      
tcp        0      0 0.0.0.0:5000            0.0.0.0:*               LISTEN      
tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN      
tcp        0      0 0.0.0.0:6379            0.0.0.0:*               LISTEN      
tcp        0      0 :::6379                 :::*                    LISTEN      
udp        0      0 127.0.0.11:44542        0.0.0.0:*                           
/romm # 

[zurdi15]

Hi! how are you connecting to the wsl romm instance? are you using the wsl IP?

I can connect to my wsl instance using directly the wsl IP

Edit: Also you may need to port forward your WSL port to windows with something like this:

netsh interface portproxy add v4tov4 listenport=[PORT] listenaddress=0.0.0.0 connectport=[PORT] connectaddress=[WSL_IP]

[FrankEBailey]

With Docker Desktop I don't believe the Docker has its own IP address. I've built several WordPress dockerfiles and never had any issues connecting on my localhost with the specified port number.

Also, I'm not seeing "connection refused" or "unable to connect" but "connection reset", which indicates that I'm able to connect to the ROMM instance, but something is immediately resetting the connection. Nothing shows up in the docker log though, which is odd.

Would someone be willing to share their own docker-compose yml file with the API keys suitably redacted?

[gantoine]

@FrankEBailey I know it's been a while but did you ever get this working?

[FrankEBailey]

@FrankEBailey I know it's been a while but did you ever get this working?

Sorry, no. I gave up.

[gantoine]

Ok sorry to hear that! For anyone else who comes across this, running in WSL2 isn't a setup we recommend or can support/help debug.