Shows Forbidden while trying to access in browser after successful build #5930

sakthivel-axim · 2022-12-28T11:07:24Z

sakthivel-axim
Dec 28, 2022

I have followed the following link to build it.
https://coder.com/docs/code-server/latest/CONTRIBUTING#build

Any solution for this will be helpful.

Code-Server - V4.9.0

Jan 4, 2023

@jsjoeio @im-coder-lg , I have cleaned existing build and taken latest tag v4.9.0. Followed the steps mentioned here (https://coder.com/docs/code-server/latest/CONTRIBUTING#build) to build the source and run.

$ quilt push -a

$ yarn 

$ yarn build 

$ VERSION='4.9.0' yarn build:vscode 

$ KEEP_MODULES=1 yarn release 

$ cd release 

$ node . -vvv

Terminal Logs

((v4.9.0))$ node . -vvv

Trace: [2023-01-04T10:46:49.148Z] trace child:5053 got message {"message":{"type":"handshake","args":{"bind-addr":"127.0.0.1:9001","auth":"password","password":"76a9b75452cc7eeb8f9f9d81","config":"/home/test/.config/code-server/config.yaml","verbose":true,"user-data-dir":"/home/test/.local/share/code-server…

View full answer

im-coder-lg · 2022-12-28T11:56:52Z

im-coder-lg
Dec 28, 2022

All I know about this is that it's familiar. Can you try searching the word forgotten in the discussion omnibar? I think the answer is in one of them.

0 replies

ccloving2007 · 2022-12-28T12:07:54Z

ccloving2007
Dec 28, 2022

network error.

0 replies

sakthivel-axim · 2022-12-29T16:07:59Z

sakthivel-axim
Dec 29, 2022
Author

Thanks @im-coder-lg , @ccloving2007

I couldn't find answer related to this.

I have seen similar discussion thread (#5797) says , it will be fixed. But, looks still it's open

0 replies

im-coder-lg · 2022-12-30T05:38:14Z

im-coder-lg
Dec 30, 2022

Maybe it is due to firewalls?

6 replies

im-coder-lg Dec 30, 2022

Well, the issue was with Termux packages, but that is not the case here...

sakthivel-axim Jan 2, 2023
Author

Thanks @im-coder-lg . Still no clue on the issue. Is there debugging levels can set while starting the service to know exact cause for this issue?

im-coder-lg Jan 2, 2023

Wait, I think you can try something like this(?)

$ code-server --logs --verbose

I think the command for verbose logs is like that... And here I am, thinking what "verbose" means 😂

jsjoeio Jan 3, 2023

are you sure you applied the patches before building?

sakthivel-axim Jan 4, 2023
Author

@jsjoeio Yes. I have applied as mentioned here https://coder.com/docs/code-server/latest/CONTRIBUTING#i-see-forbidden-access-when-i-load-code-server-in-the-browser . Please let me know if there is any other way to do it.

sakthivel-axim · 2023-01-04T10:55:37Z

sakthivel-axim
Jan 4, 2023
Author

@jsjoeio @im-coder-lg , I have cleaned existing build and taken latest tag v4.9.0. Followed the steps mentioned here (https://coder.com/docs/code-server/latest/CONTRIBUTING#build) to build the source and run.

$ quilt push -a

$ yarn 

$ yarn build 

$ VERSION='4.9.0' yarn build:vscode 

$ KEEP_MODULES=1 yarn release 

$ cd release 

$ node . -vvv

Terminal Logs

((v4.9.0))$ node . -vvv

Trace: [2023-01-04T10:46:49.148Z] trace child:5053 got message {"message":{"type":"handshake","args":{"bind-addr":"127.0.0.1:9001","auth":"password","password":"76a9b75452cc7eeb8f9f9d81","config":"/home/test/.config/code-server/config.yaml","verbose":true,"user-data-dir":"/home/test/.local/share/code-server","extensions-dir":"/home/test/.local/share/code-server/extensions","log":"trace","host":"127.0.0.1","port":9001,"proxy-domain":[],"_":[],"usingEnvPassword":false,"usingEnvHashedPassword":false}}}
    at doLog (/var/www/IDEs/code-server/release/node_modules/@coder/logger/out/logger.js:57:28)
    at ServerFormatter.doWrite (/var/www/IDEs/code-server/release/node_modules/@coder/logger/out/logger.js:204:9)
    at ServerFormatter.write (/var/www/IDEs/code-server/release/node_modules/@coder/logger/out/logger.js:119:14)
    at Logger.handle (/var/www/IDEs/code-server/release/node_modules/@coder/logger/out/logger.js:339:25)
    at Logger.trace (/var/www/IDEs/code-server/release/node_modules/@coder/logger/out/logger.js:268:14)
    at process.onMessage (/var/www/IDEs/code-server/release/out/node/wrapper.js:72:47)
    at process.emit (node:events:527:28)
    at emit (node:internal/child_process:938:14)
    at processTicksAndRejections (node:internal/process/task_queues:84:21)
Trace: [2023-01-04T10:46:49.150Z] trace Using extensions-dir ~/.local/share/code-server/extensions
    at doLog (/var/www/IDEs/code-server/release/node_modules/@coder/logger/out/logger.js:57:28)
    at ServerFormatter.doWrite (/var/www/IDEs/code-server/release/node_modules/@coder/logger/out/logger.js:200:20)
    at ServerFormatter.write (/var/www/IDEs/code-server/release/node_modules/@coder/logger/out/logger.js:119:14)
    at Logger.handle (/var/www/IDEs/code-server/release/node_modules/@coder/logger/out/logger.js:339:25)
    at Logger.trace (/var/www/IDEs/code-server/release/node_modules/@coder/logger/out/logger.js:268:14)
    at /var/www/IDEs/code-server/release/out/node/main.js:122:21
    at Generator.next (<anonymous>)
    at /var/www/IDEs/code-server/release/out/node/main.js:31:71
    at new Promise (<anonymous>)
    at __awaiter (/var/www/IDEs/code-server/release/out/node/main.js:27:12)
[2023-01-04T10:46:49.150Z] info  code-server 0.0.0 8ed7498b3c82c265afc0d3eecd4aa52a5899fe88
[2023-01-04T10:46:49.150Z] info  Using user-data-dir ~/.local/share/code-server
[2023-01-04T10:46:49.159Z] info  Using config file ~/.config/code-server/config.yaml
[2023-01-04T10:46:49.159Z] info  HTTP server listening on http://127.0.0.1:9001/ 
[2023-01-04T10:46:49.159Z] info    - Authentication is enabled
[2023-01-04T10:46:49.159Z] info      - Using password from ~/.config/code-server/config.yaml
[2023-01-04T10:46:49.159Z] info    - Not serving HTTPS 
Trace: [2023-01-04T10:47:03.546Z] trace heartbeat
    at doLog (/var/www/IDEs/code-server/release/node_modules/@coder/logger/out/logger.js:57:28)
    at ServerFormatter.doWrite (/var/www/IDEs/code-server/release/node_modules/@coder/logger/out/logger.js:200:20)
    at ServerFormatter.write (/var/www/IDEs/code-server/release/node_modules/@coder/logger/out/logger.js:119:14)
    at Logger.handle (/var/www/IDEs/code-server/release/node_modules/@coder/logger/out/logger.js:339:25)
    at Logger.trace (/var/www/IDEs/code-server/release/node_modules/@coder/logger/out/logger.js:268:14)
    at Heart.<anonymous> (/var/www/IDEs/code-server/release/out/node/heart.js:41:29)
    at Generator.next (<anonymous>)
    at /var/www/IDEs/code-server/release/out/node/heart.js:8:71
    at new Promise (<anonymous>)
    at __awaiter (/var/www/IDEs/code-server/release/out/node/heart.js:4:12)
[16:17:03] 




[16:17:03] Extension host agent started.
[2023-01-04T10:47:17.186Z] debug redirecting from / to ./login
[2023-01-04T10:47:24.717Z] debug no valid cookie domain {"host":"127.0.0.1"}
[2023-01-04T10:47:24.717Z] debug redirecting from /login to ./
[2023-01-04T10:47:24.762Z] debug redirecting from / to ./?folder=~/.local/share/code-server

Browser Screenshot

13 replies

sakthivel-axim Jan 9, 2023
Author

Thanks @jsjoeio , @code-asher . I have taken the latest source V4.9.1 and followed the below steps. It's working, didn't face any issues with development build. Didn't build vscode explicitly.

$ git clone [email protected]:coder/code-server.git 

$ git checkout  v4.9.1 

$ quilt push –a 

$ quilt refresh 

$ yarn 

$ yarn build 

$ VSCODE_DEV=1 node . -vvv 

 

Installed extension using following command 

Downloaded extension (Compilation and debugging works using this extension for C/C++)  

$ node . --install-extension [~/Downloads/[email protected]](mailto:~/Downloads/[email protected])

Launch.json

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "gcc - Build and debug active file",
            "type": "cppdbg",
            "request": "launch",
            "program": "${fileDirname}/${fileBasenameNoExtension}",
            "args": [],
            "stopAtEntry": false,
            "cwd": "${fileDirname}",
            "environment": [],
            "externalConsole": false,
            "MIMode": "gdb",
            "setupCommands": [
                {
                    "description": "Enable pretty-printing for gdb",
                    "text": "-enable-pretty-printing",
                    "ignoreFailures": true
                },
                {
                    "description": "Set Disassembly Flavor to Intel",
                    "text": "-gdb-set disassembly-flavor intel",
                    "ignoreFailures": true
                }
            ],
            "preLaunchTask": "C/C++: gcc build active file",
            "miDebuggerPath": "/usr/bin/gdb"
        }
    ]
}

Tasks.json

{
    "tasks": [
        {
            "type": "cppbuild",
            "label": "C/C++: gcc build active file",
            "command": "/usr/bin/g++",
            "args": [
                "-fdiagnostics-color=always",
                "-g",
                "${file}",
                "-o",
                "${fileDirname}/${fileBasenameNoExtension}"
            ],
            "options": {
                "cwd": "${fileDirname}"
            },
            "problemMatcher": [
                "$gcc"
            ],
            "group": {
                "kind": "build",
                "isDefault": true
            },
            "detail": "Task generated by Debugger."
        }
    ],
    "version": "2.0.0"
}

jsjoeio Jan 9, 2023

Hooray!

sakthivel-axim Jan 10, 2023
Author

Thanks @jsjoeio. Do you have any steps to compile & run programs instead of using launch.json/tasks.json

jsjoeio Jan 10, 2023

I don't do any C++ but for Node/Web apps, I simply run npm start in the Integrated Terminal. Sorry, that's probably not much help!

sakthivel-axim Jan 11, 2023
Author

OK. Thanks @jsjoeio .

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Shows Forbidden while trying to access in browser after successful build #5930

{{title}}

Replies: 5 comments 19 replies

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Shows Forbidden while trying to access in browser after successful build #5930

Replies: 5 comments · 19 replies

sakthivel-axim Dec 29, 2022 Author

sakthivel-axim Jan 2, 2023 Author

sakthivel-axim Jan 4, 2023 Author

sakthivel-axim Jan 4, 2023 Author

sakthivel-axim Jan 9, 2023 Author

sakthivel-axim Jan 10, 2023 Author

sakthivel-axim Jan 11, 2023 Author

Replies: 5 comments 19 replies

sakthivel-axim
Dec 29, 2022
Author

sakthivel-axim Jan 2, 2023
Author

sakthivel-axim Jan 4, 2023
Author

sakthivel-axim
Jan 4, 2023
Author

sakthivel-axim Jan 9, 2023
Author

sakthivel-axim Jan 10, 2023
Author

sakthivel-axim Jan 11, 2023
Author