-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
Unable to connect with --link #2734
Comments
Downgrading to version 3.8.0 did not help resolve the issue, I have a feeling this may be an issue on cdr's end. I have tried getting this to work in both GCP and DigitalOcean to no avail. |
Tried to repro this but could not - do you have any additional steps that could help in reproducing it? |
Honestly not really, it's a very strange issue. I installed |
I have tried deleting the |
Update: after turning on my VPN, I seem to be able to connect to the server now, however I don't see why I would need to do that. |
Did it give you an error ID? We can use that to investigate further. |
I have the same problem
Any ideas? |
A temporary fix is to use a VPN and set the region to the region of where
your server is currently located, however that's just my advice and you
should wait for what the devs have to say.
…On Mon, Feb 22, 2021 at 5:26 PM parslov ***@***.***> wrote:
I have the same problem
- brand new AWS instance
- AWS free tier
- Ubuntu 20.04
- Installed with code-server with this (from
https://github.com/cdr/code-server): curl -fsSL
https://code-server.dev/install.sh | sh
- Opened HTTP, HTTPS, Custom TCP (pot 8080), and SSH in inbound rules
- Started code-server with: code-server --link
- ...and then opened Safari on my mac and entered the https-address
shown
- ...and then get: 'Error connecting to your code-server instance'
Any ideas?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#2734 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADLUVG7GUNLGODXJUIFJISTTAJLPRANCNFSM4XW2NRYQ>
.
|
@parslov Did it give you an error ID? Does it persist if you visit the the https address a second time? |
I did not get an error id. Today I went through the same process on Google Cloud, using Ubuntu 16 and opening for HTTP and HTTPS. Same result. |
OK, thanks! I'll see what we can turn up. |
Note, I have never gotten an ID from when this error has popped up. |
Makes sense, turns out I was wrong about the error ID. We don't log connection errors since they don't provide any information (just things like |
Has there been any update on this situation? |
Just wondering if theres been any further development on this issue? |
We haven't since the connection errors don't provide any extra details on our end. I think what we'll have to do is try to replicate it ourselves and go from there. |
@SamHep0803 I can take a look at this seeing that it's iPad. Do you mind providing reproduction steps? I have my own setup on iPad but ideally I try to mimic yours as closely as possible. |
Spoke to the developer working on this before. We're going to aim to get this fixed before May 1st. Until then the workaround is to use a VPN and set the region of where your server is located. |
Hi, has there been any update on this issue? |
I managed to finally get it working by running a server on Oracle Cloud in Germany using the —link option. I am accessing the server from Denmark. Not sure if Germany and Denmark are in the same ‘region’. I did not have to use VPN but of course set up the server side to accept traffic on the relevant ports. |
Hi @SamHep0803! So I spoke to the developer working on this. He had another priority come up and wasn't able to finish it last week. It's in progress but I don't have an ETA on when it will be done. Feel free to ping this issue again in two weeks! |
Looks like this is still happening. Any updates? |
Unfortunately, no updates. I reached out to the developer but haven't heard back yet. |
Been more then a month now, still no update? |
Apologies. We're a small team (code-server). I'll ping them again and see if I can get any update. Worst case: they come back and say we won't be able to fix it. Best case: they say they can and I can share more information. Other scenario: if I could collect data and say, "this is affecting X number of users in the code-server community and we should prioritize" then that might help. Give this message a 👍 if you're experiencing this issue still. |
Okay I got a response. I spoke to the developer. We're working on some networking changes in the enterprise product going from WebSockets to WebRTC. Eventually those changes will make their way into coder-cloud (powers |
That's great news! Good to finally see some progress on this issue.
Thanks a lot for your efforts and hopefully we can have this issue resolved
in the near future.
…On Tue, Jul 20, 2021 at 9:58 PM Joe Previte ***@***.***> wrote:
Okay I got a response.
I spoke to the developer. We're working on some networking changes in the
enterprise product going from WebSockets to WebRTC. Eventually those
changes will make their way into coder-cloud (powers --link +
code-server) in which case, will solve this issue. I don't have an ETA but
will share updates on this thread as I have them
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2734 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADLUVGZZ3D23NEQNHCOQ2FLTYWTJVANCNFSM4XW2NRYQ>
.
|
I hope so too and thank you for understanding. |
This is nice there is a good chain here. Learning how to github / programming because of you guys... so thanks for having a great product and am looking forward to the correction. It appears for me that it times out, if I haven't done anything in the system I feel like cdr.co just terminates the connection. (It's free so, hey... i get it.) But these are the similar errors I am getting. As the project develops more will --link be intergrated? I'd be willing to pay some monies to get it running. I love being able to go to a webpage and keep coding. |
Hmm...that's unusual. Do you mind telling us a bit about your setup?
Hopefully, but don't want to make any promises. We are having internal discussions about improving and better integrating and promoting --link.
If you ever want to chat more about that, feel free to shoot me an email joe@coder.com — we do have some things in the pipeline so otherwise you'll have to keep an eye out! |
Went from Italy to Portugal, it worked in Italy but now it doesn't work here in Lisbon. I'm running it off the Frankfurt region in GCP. Restarting or rebooting don't solve the issue. |
It looks like the link project has been shelved, possibly indefinitely. I am not sure how far the rewrite got but it seems not far enough before the plug was pulled. I think the only thing we can recommend now is to set up a domain and a reverse proxy, possibly Caddy since it handles certificates for you or with some of the other methods listed here: https://github.com/coder/code-server/blob/main/docs/guide.md#setup-guide |
|
code-server --version
: 3.9.0 fc6d123When running
code-server --link
, the process starts successfully however when you go to the link given in the server output, the errorError connecting to your code-server instance
shows up when you go to the site.Initially, no error gets thrown in the terminal however after around 1 hour,
[2021-02-16T09:59:22.641Z] info 2021/02/16 09:59:22 [ERR] yamux: Failed to read header: failed to get reader: failed to read frame header: EOF
[2021-02-16T09:59:22.645Z] info 2021-02-16 09:59:22.644 [WARN] <proxy.go:48> code-server proxy exited {"error": "accept tcp [::]:36221: use of closed network connection"}
is logged.
Thanks, Sam.
The text was updated successfully, but these errors were encountered: