### Is there an existing issue for this? - [X] I have searched the existing issues ### OS/Web Information - Web Browser: Edge 107.0.1418.62 - Local OS: Windows 11 Pro - Remote OS: Debian GNU/Linux 11 (bullseye) - Remote Architecture: aarch64 - `code-server --version`: 1.72.1 129500ee4c8ab7263461ffe327268ba56b9f210d arm64 ### Steps to Reproduce 1. Create a nextjs project 2. Start the server 3. Go to the proxy url 4. See how nextjs tries to get the files from "domain.com/x" instead of "domain.com/proxy/3000". ### Expected To be able to use the nextjs server without the error that the assets are not found. ### Actual Errors about files in the _next/static folder not being found. ### Logs _No response_ ### Screenshot/Video  ### Does this issue happen in VS Code or GitHub Codespaces? - [X] I cannot reproduce this in VS Code. - [X] I cannot reproduce this in GitHub Codespaces. ### Are you accessing code-server over HTTPS? - [X] I am using HTTPS. ### Notes _No response_
Activity
jsjoeio commentedon Dec 5, 2022
You need to use the
/absxproxyinstead.In your
next.config.js:Then access it at
http://localhost:8080/absproxy/3000References:
sawa-ko commentedon Dec 5, 2022
Hi that only works for js files (bundle files) but when you try to use files from public folder it doesn't work.
Trying to use files like this gets a 404 error because the browser tries to get them from the root domain.