You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hi
i have bought a vps and a domain and i installed the go-http-tunnel in server and client side i can see the client connects to server but when i type the host i did in tunnel.yml it returns client not subscribed im realy confused because yesterday it was just working but suddnly it showd this problem
the command shows in server side :
level 0 action round trip failed addr myhome_ip:62003 host my-domain.xyz url /favicon.ico err client not subscribed
and in client side :
2021/04/09 22:06:43 config server_addr: vps_ip:5223
tls_crt: client.crt
tls_key: client.key
root_ca: ""
backoff:
interval: 500ms
multiplier: 1.5
max_interval: 1m0s
max_time: 15m0s
tunnels:
webui:
proto: http
addr: http://192.168.1.19:3218
host: .webui.myip.xyz
it was a domain problem and it worked again but when i want to connect to my node-red it says lost connection
I have encountered this problem. Please tell me how you solved it?
hi
i have bought a vps and a domain and i installed the go-http-tunnel in server and client side i can see the client connects to server but when i type the host i did in tunnel.yml it returns client not subscribed im realy confused because yesterday it was just working but suddnly it showd this problem
the command shows in server side :
level 0 action round trip failed addr myhome_ip:62003 host my-domain.xyz url /favicon.ico err client not subscribed
and in client side :
2021/04/09 22:06:43 config server_addr: vps_ip:5223
tls_crt: client.crt
tls_key: client.key
root_ca: ""
backoff:
interval: 500ms
multiplier: 1.5
max_interval: 1m0s
max_time: 15m0s
tunnels:
webui:
proto: http
addr: http://192.168.1.19:3218
host: .webui.myip.xyz
2021/04/09 22:06:43 level 1 action start
2021/04/09 22:06:43 level 1 action dial network tcp addr vps_ip:5223
2021/04/09 22:06:44 level 1 action handshake addr 65.21.105.2
The text was updated successfully, but these errors were encountered: