-
-
Notifications
You must be signed in to change notification settings - Fork 174
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
Need help with running et over a reverse tunnel #678
Comments
What OS are you running on the server? That's a strange protobuf error |
I am running Ubuntu 24.04.1 on the remote server and Arch on the local server. On the Ubuntu remote server, I have |
I think we should start building static binaries. But for now, can you try
building et from source and replacing the etserver and etterminal binaries
in /usr/bin with the ones you built?
…On Wed, Dec 11, 2024, 6:50 PM Bang C. Huynh ***@***.***> wrote:
I am running Ubuntu 24.04.1 on the remote server and Arch on the local
server. On the Ubuntu remote server, I have et/noble,now 6.2.9-noble1
amd64 and libprotobuf32t64/noble,now 3.21.12-8.2build1 amd64. On the Arch
local server, I have eternalterminal 6.2.9-1 and protobuf 28.3-1.
—
Reply to this email directly, view it on GitHub
<#678 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACK5PZIMQJ5KGFS2LGMUND2FDMUZAVCNFSM6AAAAABSSTFUFKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZXGUYDKMJUG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I have tried compiling et from source using these instructions (https://github.com/MisterTea/EternalTerminal#debianubuntu), but still run into more or less the same error:
|
Apologies if this is a very naive request for help, but I've not been having any success getting EternalTerminal to work over a reverse tunnel, probably due to my limited experience with networking.
I have a local server behind a NAT, but I would like to ssh into this server publicly. I have access to a public remote server (a Google Cloud VM instance), so from my local server, I can set up remote port forwarding with
which allows me to access the local server from the remote server via port 2222 without any problem:
I have also created an entry in the ssh config file on the remote server like so:
and
works fine.
However, if I try
after successfully authenticating, I get
Rerunning with
--verbose=9
and--logtostdout
givesI have ensured that port 2022 is opened on the local server, and running
et
locally on the local server works fine. So I am not sure how to get EternalTerminal to work with the reverse tunnel. Perhaps something to do with me not forwarding the right ports? I'd appreciate any help. Many thanks!The text was updated successfully, but these errors were encountered: