whitesoup12
CCoder.com
•Created by whitesoup12 on 5/6/2025 in #help
ReactJS App Subdomain
Nope, all good! Just user error on my part. I appreciate the follow up!
21 replies
CCoder.com
•Created by whitesoup12 on 5/6/2025 in #help
ReactJS App Subdomain
Yeah, I’m logged in as the same user. I did also notice I had a typo in my workspace name. When I was trying to port forward, I was spelling it without the typo. 🤦. So it does work without the user as well.
21 replies
CCoder.com
•Created by whitesoup12 on 5/6/2025 in #help
ReactJS App Subdomain
No, I own it. I was just using the wrong workspace name.
21 replies
CCoder.com
•Created by whitesoup12 on 5/6/2025 in #help
ReactJS App Subdomain
Update. I was finally able to get
port-forward working. I tried a multitude of workspace names before finding out coder list will give the workspaces the CLI uses (which was user/workspace). With port-forward working I can now access all parts of the app.21 replies
CCoder.com
•Created by whitesoup12 on 5/6/2025 in #help
ReactJS App Subdomain
To clarify, I'm not actually using
localhost to access my apps. I'm. using my coder URL (eg. ****.try.coder.app:5173). It's when I try to access subdomain.****.try.coder.app that I have the issue. The ReactJS app actually just grabs the subdomain and displays a different section of the app, so technically not a real subdomain. As for coder port-forward, I have yet to get that to work. My workspace name for UI is RemoteFalconUI, but when I try to port forward, I always end up with an error. coder port-forward RemoteFalconUI --tcp 5173:5173
Encountered an error running "coder port-forward", see "coder port-forward --help" for more information
error: Resource not found or you do not have access to this resource21 replies