I can’t get the forge tunnel-CustomUI live update to work in one of my forge apps. Without the port setting in the manifest.yml file, the page is loaded. But it doesn’t load the changes to the customui. If I add resources/tunnel/port setting to the manifest.yml file, I get the following exception in the browser console; the page is not loaded at all.
Uncaught
Exception { name: "NS_ERROR_CONTENT_BLOCKED", message: "", result: 2153644038, filename: "http://localhost:8000/static/js/bundle.js", lineNumber: 35390, columnNumber: 0, data: null, stack: "WebSocketClient@http://localhost:8000/static/js/bundle.js:35390:19\ninitSocket@http://localhost:8000/static/js/bundle.js:36792:12\n./node_modules/webpack-dev-server/client/index.js?protocol=ws%3A&hostname=0.0.0.0&port=3000&pathname=%2Fws&logging=none&overlay=%7B%22errors%22%3Atrue%2C%22warnings%22%3Afalse%7D&reconnect=10&hot=true&live-reload=true@http://localhost:8000/static/js/bundle.js:35740:55\noptions.factory@http://localhost:8000/static/js/bundle.js:46139:31\n__webpack_require__@http://localhost:8000/static/js/bundle.js:45596:33\n@http://localhost:8000/static/js/bundle.js:46719:30\n@http://localhost:8000/static/js/bundle.js:46723:12\n" }
WebSocketClient.js:16
Also on the forge console, it prints the falling warning.
Received proxy request. Serving file index.html for resource forge-terminal from specified address http://localhost:3000
CSP violation detected for 'connect-src' while serving content at http://localhost:8000/
I have added the following section to the manifest, build/redeploy/upgrade and it didn’t help.
permissions:
content:
styles:
- "unsafe-inline"
scripts:
- "unsafe-inline"
- "unsafe-eval"
I have cross-checked index.html, and manifest.yml files with a previous app but I couldn’t find a difference that may cause this issue.