Closed fbotp closed 8 months ago
Thanks for the report. I will have a quick look at it now.
@fbotp I found there is no changes related to socket.io-client
API between v0.5.2
and v0.5.3
, except for an internal timeout
exception which should not trigger 502 error.
Could you please attach the normal log starts with SocketIOAPI
? Thank you.
I have just searched "502 error for socketio client" online and found this link maybe helpful:
https://stackoverflow.com/questions/35698595/bad-gateway-error-using-socket-io-node-js-over-ssl
Please check if your server address is correctly using "http://" or "https://". "http://" maybe wrong for SSL-enabled server.
@iamhyc Thank you for your reply. Now I am using v0.5.2
. When I enter the project called 面向战略性新兴产业的专名标引方法研究
, the vscode log looks like this:
where 192.168.3.149:6180
is self-hosted server ,and if I use v0.5.3
, the log looks like:
As you see, the error keeps reoccurring and doesn't stop
I think below picture shows that I have logged in.
By the way, I'm sure my address is http://192.168.3.149:6180/
. And if now I install v0.5.2
and reload window, files in project would appearred normally.
Got it. That is weird. I will check on sharelatex v4.2
later.
thanks, waiting for your reply❤️
Cannot produce the bug on my side. I have to say this is really weird, especially considering there is no much difference between v0.5.2
and v0.5.3
.
Can you try to remove the server firstly, then add the server and login to see if it works?
Though it is not able to reproduced, I find the server may prefer v2
connection by default.
Please have a try with the auto-generated temporary extension here: https://github.com/iamhyc/Overleaf-Workshop/actions/runs/7488723638?pr=75
It will use v2
connection if the error is thrown.
I tried remove server and add again, I also use this temp extension, but it does't work, the error logs just like above. I suddenly remembered that I ran the following commands within the sharelatex container:
tlmgr option repository https://mirrors.tuna.tsinghua.edu.cn/CTAN/systems/texlive/tlnet
tlmgr update --self --all
tlmgr install scheme-full
I'm not sure if it will affect this.
I rechecked all my operations: pulled sharelatex/sharelatex:4.2.0
from hub.docker.com using overleaf-toolkit
, went into the container to install scheme-full
, and created an admin user via launchpad
, uploaded the project, then added the server in vscode, and tried to enter the project, and then found these error. Are there any operating errors?
I rechecked all my operations: pulled
sharelatex/sharelatex:4.2.0
from hub.docker.com usingoverleaf-toolkit
, went into the container to installscheme-full
, and created an admin user vialaunchpad
, uploaded the project, then added the server in vscode, and tried to enter the project, and then found these error. Are there any operating errors?
I did exactly the same thing, exccept to install scheme-full
.
Can you test on just creating an example project?
Please also help test the new temporary extension and attach the log: https://github.com/iamhyc/Overleaf-Workshop/actions/runs/7489218302
I found I made some mistake in last one.
I used this extension and 502 errors keep appearing.
Please also help test the new temporary extension and attach the log: https://github.com/iamhyc/Overleaf-Workshop/actions/runs/7489218302
I found I made some mistake in last one.
Ok, at least we know there is nothing to do with v2
api. The cause is still unknown.
I'm trying to recreate a server without "scheme-full" to see if this has something to do with it
I did these:
git clone https://github.com/overleaf/toolkit.git ./test
cd test
./bin/init
# then modify two variable in `config/overleaf.rc`, because server have no gui, and 80 port has another web server:
SHARELATEX_LISTEN_IP=0.0.0.0
SHARELATEX_PORT=6180
./bin/up
then visited http://192.168.3.149:6180/launchpad
and create user, then created an example project named test
, then added this server in vscode, and tried to enter this project. It still failed.
Then I believe you should blame your router or gateway. Though I still got no idea why v0.5.2
works ...
Just to make sure: have you tried http://127.0.0.1:6180
?
No, I ran this server on a linux server and visit it on my PC, so I don't know how to visited it by http://127.0.0.1:6180
No, I ran this server on a linux server and visit it on my PC, so I don't know how to visited it by
http://127.0.0.1:6180
Use vscode SSH-Remote Extension and then install this extension in remote.
I forawrd 6180 to PC localhost, and add server http://127.0.0.1:6180
, it works, but why
I forawrd 6180 to PC localhost, and add server
http://127.0.0.1:6180
, it works, but why
I am not sure how you do the forward, but the websocket protocol maybe unstable in your environment. I guess.
I found that, if I install extension on server, and connect to remote server by Remote-SSH
first, then get into project, it works, if I connect to overleaf in a new vscode window, it will fail. So everytime I connect to overleaf, I need to ssh to server firstly?
I think the problem is: you can connect to the server via 127.0.0.1
but not 192.168.3.149
.
In my network environment, I can connect to it via both 127.0.0.1
and 100.64.0.3
(virtual LAN address).
So, I don't think this is a general issue and I suggest you check your network router firstly.
~But I feel a little strange, why can I access it through the web page but not through vscode? And there will be no problem logging in, getting the project list, creating a new project, or deleting the project.~ Ok, it's my pc problem, thank you. So sorry to bother you.
But I feel a little strange, why can I access it through the web page but not through vscode? And there will be no problem logging in, getting the project list, creating a new project, or deleting the project.
You make the reply so fast and I am still typing ...
Could you also let me know why? I am still curious about the difference between v0.5.2
and v0.5.3
Sorry, I installed v2rayA
on my PC, and use system proxy
mode, and config RoutingA
as below:
default: direct domain(arxiv.org)->proxy domain(debrepo.freedownloadmanager.org)->proxy domain(files.pythonhosted.org)->proxy domain(geosite:docker)->proxy domain(geosite:facebook)->proxy domain(geosite:github)->proxy domain(geosite:google)->proxy domain(geosite:medium)->proxy domain(geosite:openai)->proxy domain(geosite:quora)->proxy domain(geosite:reddit)->proxy domain(geosite:stackexchange)->proxy domain(huggingface.co)->proxy domain(ppa.launchpadcontent.net)->proxy domain(pypi.org)->proxy domain(steamcommunity.com)->proxy domain(steampowered.com)->proxy domain(steamunlocked.net)->proxy domain(geosite:twitter)->proxy domain(geosite:v2ray)->proxy domain(v2ex.com)->proxy domain(v2raya.org)->proxy domain(www.popai.pro)->proxy domain(chat.forefront.ai)->proxy domain(geosite:wikimedia)->proxy
It seems that, if I set network proxy in windows, it does't work, but if I close it in Windows settings, it will be okay.
I just found that, even if I set all domain as direct mode
, this extension still doesn't work. It's so strange. Anyway, thanks a lot!
Yes, I should have warned you of the proxy thing firstly. Anyway, glad that you find the root cause!
Yes, I changed http.proxy support
to off
in vscode, and everything works fine! Thank you for your patient answer!
Describe the bug
Expected behavior
How To Reproduce
Environment
[Optional] Developer Logs