Skip to content

On Arch Linux server password param doesn't work, and ENOENT error on diretory that's not working directory #62

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
leetNightshade opened this issue Mar 7, 2019 · 2 comments
Labels
bug Something isn't working waiting-for-info Waiting for more information from submitter

Comments

@leetNightshade
Copy link

leetNightshade commented Mar 7, 2019

Problems

  1. Server password param doesn't work
  2. ENOENT error on working directory, trying to access subfolder that doesn't exist.
  3. Website is a blank screen after login, probably related to problem 2 directly above.
  4. Output version is 0.0.0 instead of 1.31.1-100.

Info

  • code-server version: server/0.0.0 linux-x64 node-v8.9.3 I had downloaded 1.31.1-100 from code-server-1.31.1-100-linux-x64.tar.gz
  • OS Version: Linux archlinux 4.20.12-arch1-1-ARCH terminal becomes unresponsive after socket disconnect #1 SMP PREEMPT Sat Feb 23 15:11:34 UTC 2019 x86_64 GNU/Linux on Linode
  • Setup is running code-server in a webdirectory through nginx.

Steps to Reproduce

  1. Setup systemd ide.service to run code-server as a user, in my case http, same as web user process for php and mysql.
  2. Run code-server --password=testing
    Notice when trying to enter password the generated one is what works, not the passed in one.
  3. ENOENT on /working/directory/here/plus/Backups/workspace.json. It seems to be looking for a Backups folder in my working directory, and a workspace file that doesn't yet exist.
  4. When running code-server --version for this bug, it output 0.0.0 for the server version.
@kylecarbs
Copy link
Member

There's a caching issue with the assets since files are named the same on the password-prompt and IDE bundles. You can try clearing your cache.

@nhooyr nhooyr added waiting-for-info Waiting for more information from submitter bug Something isn't working labels Mar 8, 2019
@code-asher
Copy link
Member

All asset names and paths are unique now so this should be solved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working waiting-for-info Waiting for more information from submitter
Projects
None yet
Development

No branches or pull requests

4 participants