'Network Error' When Accessinging Wasp App From Mobile Device
Hi all! I've made some exciting progress on a Wasp app I have been building, and I want to test it out on my physical iPhone connected to the same WiFi network as my desktop that is running my dev server. I am not a networking guru, so I apologize if the following question is silly:
What is not working: When I navigate to my app login page via my desktop's private IP on my phone, (192.168.1.17:3000/login), I am presented with the Wasp login page, per usual. But when I attempt to actually login with a valid account, I get a 'Network Error' toast
What I have done:
1 - Followed the Wasp docs (https://wasp.sh/docs/advanced/middleware-config) section 1 to create
For kicks, I have also tried
2 - Via Windows Powershell admin, ran the following two commands to port forward to WSL running the Wasp dev server:
and
where
3 - Via Windows Defender Firewall, created a rule to allow inbound TCP traffic for local ports 3000 and 3001 on private networks (Which is what my home network is defined as in Windows network settings)
4 - Stopped and restarted my Wasp dev server several times & ran
5 - Restarted my computer (Confirmed that my WSL private IP did not change and my port forwarding rules persisted)
Any help appreciated, thanks!
What is not working: When I navigate to my app login page via my desktop's private IP on my phone, (192.168.1.17:3000/login), I am presented with the Wasp login page, per usual. But when I attempt to actually login with a valid account, I get a 'Network Error' toast
What I have done:
1 - Followed the Wasp docs (https://wasp.sh/docs/advanced/middleware-config) section 1 to create
src/serverSetup.tsFor kicks, I have also tried
http://192.168.1.17:3000https://192.168.1.17:30002 - Via Windows Powershell admin, ran the following two commands to port forward to WSL running the Wasp dev server:
netsh interface portproxy add v4tov4 listenport=3000 listenaddress=0.0.0.0 connectport=3000 connectaddress=172.19.112.174and
netsh interface portproxy add v4tov4 listenport=3001 listenaddress=0.0.0.0 connectport=3001 connectaddress=172.19.112.174where
172.19.112.1743 - Via Windows Defender Firewall, created a rule to allow inbound TCP traffic for local ports 3000 and 3001 on private networks (Which is what my home network is defined as in Windows network settings)
4 - Stopped and restarted my Wasp dev server several times & ran
wasp clean5 - Restarted my computer (Confirmed that my WSL private IP did not change and my port forwarding rules persisted)
Any help appreciated, thanks!
Wasp comes with a minimal set of useful Express middleware in every application. While this is good for most users, we realize some may wish to add, modify, or remove some of these choices both globally, or on a per-api/path basis.
