MisterTea
commented
1 month ago It's failing to read from the terminal, strange. I'm truly at a loss at what could cause a terminal read to fail?
On Sat, Oct 5, 2024, 9:19 PM menkaur @.***> wrote:
I have a working i2p configuration to connect to my server and I decided to duplicate it changing the port to use with et. here is the content of my /etc/i2pd/tunnels.conf file: client: [ET-CLIENT] type = client host = 127.0.0.1 port = 7623 inbound.length = 1 outbound.length = 1 inbound.quantity = 5 outbound.quantity = 5 inbound.backupQuantity = 2 outbound.backupQuantity = 2 i2cp.dontPublishLeaseSet = true destination = .... destinationport = 2022 keys = ssh-in.dat gzip = true
server [ET-SERVER] type = server host = 127.0.0.1 port = 2022 inport = 2022 keys = ssh-in.dat gzip = false accesslist = .... inbound.length = 1 outbound.length = 1 inbound.quantity = 5 outbound.quantity = 5 inbound.backupQuantity = 2 outbound.backupQuantity = 2 i2cp.reduceOnIdle = true
I have obviously checked that i2p works, and this works with ssh on port 22 I have installed et on client and server and verified that the conventional connection works
I'm trying to connect from client to server with following command: et -p 7623 -v 1 @.***
this fails with: Error in authentication with etserver: Error: Connection error communicating with et daemon: No such file or directory.
, please make sure you don't print anything in server's .bashrc/.zshrc
/tmp/etterminal...log looks like follows: [INFO 2024-10-05 18:16:39,604 terminal-main PipeSocketHandler.cpp:58] Connected to endpoint /var/run/etserver.idpasskey.fifo [INFO 2024-10-05 18:16:39,604 terminal-main PipeSocketHandler.cpp:86] 6 is a good socket [FATAL 2024-10-05 18:16:41,873 terminal-main UserTerminalHandler.cpp:107] Stack Trace: [0] 0x894b4 [1] 0x8a58a [2] 0x2a948 [3] 0x79fc16434e08 [4] 0x79fc16434ecc __libc_start_main [5] 0x2ca05 Error: (2): No such file or directory [WARNING 2024-10-05 18:16:41,873 terminal-main UserTerminalHandler.cpp:107] Aborting application. Reason: Fatal log at [/home/myuser/.cache/yay/eternalterminal/src/EternalTerminal-et-v6.2.9/src/terminal/UserTerminalHandler.cpp:107]
and the client side log: Setting up and starting sentry TERM environment variable not set. Shutting down sentry
Server os is Arch, client is Gentoo
— Reply to this email directly, view it on GitHub https://github.com/MisterTea/EternalTerminal/issues/661, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACK5P26XDKPSD3DO22XQO3Z2CMZZAVCNFSM6AAAAABPN3ZL6CVHI2DSMVQWIX3LMV43ASLTON2WKOZSGU3DQNBSGA3DQNA . You are receiving this because you are subscribed to this thread.Message ID: @.***>
I have a working i2p configuration to connect to my server and I decided to duplicate it changing the port to use with et. here is the content of my /etc/i2pd/tunnels.conf file: client: [ET-CLIENT] type = client host = 127.0.0.1 port = 7623 inbound.length = 1 outbound.length = 1 inbound.quantity = 5 outbound.quantity = 5 inbound.backupQuantity = 2 outbound.backupQuantity = 2 i2cp.dontPublishLeaseSet = true destination = .... destinationport = 2022 keys = ssh-in.dat gzip = true
server [ET-SERVER] type = server host = 127.0.0.1 port = 2022 inport = 2022 keys = ssh-in.dat gzip = false accesslist = .... inbound.length = 1 outbound.length = 1 inbound.quantity = 5 outbound.quantity = 5 inbound.backupQuantity = 2 outbound.backupQuantity = 2 i2cp.reduceOnIdle = true
I have obviously checked that i2p works, and this works with ssh on port 22 I have installed et on client and server and verified that the conventional connection works
I'm trying to connect from client to server with following command: et -p 7623 -v 1 myuser@localhost
this fails with: Error in authentication with etserver: Error: Connection error communicating with et daemon: No such file or directory.
, please make sure you don't print anything in server's .bashrc/.zshrc
/tmp/etterminal...log looks like follows: [INFO 2024-10-05 18:16:39,604 terminal-main PipeSocketHandler.cpp:58] Connected to endpoint /var/run/etserver.idpasskey.fifo [INFO 2024-10-05 18:16:39,604 terminal-main PipeSocketHandler.cpp:86] 6 is a good socket [FATAL 2024-10-05 18:16:41,873 terminal-main UserTerminalHandler.cpp:107] Stack Trace: [0] 0x894b4 [1] 0x8a58a [2] 0x2a948 [3] 0x79fc16434e08 [4] 0x79fc16434ecc __libc_start_main [5] 0x2ca05 Error: (2): No such file or directory [WARNING 2024-10-05 18:16:41,873 terminal-main UserTerminalHandler.cpp:107] Aborting application. Reason: Fatal log at [/home/myuser/.cache/yay/eternalterminal/src/EternalTerminal-et-v6.2.9/src/terminal/UserTerminalHandler.cpp:107]
and the client side log: Setting up and starting sentry TERM environment variable not set. Shutting down sentry
Server os is Arch, client is Gentoo