Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[!] ERROR: sorry, it was not possible to establish a connection to the server. #157

Open
arjvy001 opened this issue Jan 31, 2024 · 7 comments
Assignees

Comments

@arjvy001
Copy link

After i start the nipe and check for status , always this error happens ,
[!] ERROR: sorry, it was not possible to establish a connection to the server.

@htrgouvea htrgouvea self-assigned this Jan 31, 2024
@htrgouvea
Copy link
Owner

Hi @arjvy001,

I need more informations about your env, like: what's is the linux distro? Version of perl, iptables or tor... The more information you can provide me, the better. This helps me to replicate the error.

Didn't you have any problems while installing the dependencies?

Thanks!

@arjvy001
Copy link
Author

Linux kali 6.5.0-kali3-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.5.6-1kali1 (2023-10-09) x86_64 GNU/Linux

This is perl 5, version 36, subversion 0 (v5.36.0) built for x86_64-linux-gnu-thread-multi

iptables v1.8.10 (nf_tables)

Tor 0.4.8.10 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.11, Zlib 1.2.13, Liblzma 5.4.5, Libzstd 1.5.5 and Glibc 2.37 as libc.

Didn't you have any problems while installing the dependencies? No

@MisileLab
Copy link

MisileLab commented Feb 27, 2024

@htrgouvea @arjvy001
I got same error, but I fixed.
you need to install some dependencies for ssl support.
http::tiny can_ssl value

5990IO::Socket::SSL 1.42 must be installed for https support
Net::SSLeay 1.49 must be installed for https support

Installed dependencies (nixos)

NetSSLeay, IOSocketSSL

I can't do pr cause I dont know about perl packaging for other os

@vstavrinov
Copy link

I have the same problem under Debian/sid

@CHFR91
Copy link

CHFR91 commented Apr 28, 2024

As I have the same problem, here is all the info:

Hello

I did first a "git pull" to be sure that I have the latest version of Nipe.

My computer:
OS: Kali GNU/Linux Rolling x86_64
Host: Inspiron 15 3515 1.8.0
Kernel: 6.6.15-amd64
CPU: AMD Ryzen 5 3450U with Radeon Vega Mobile Gfx (8) @ 2.100GHz
GPU: AMD ATI Radeon Vega Series / Radeon Vega Mobile Series
Memory: 1116MiB / 5817MiB

This is perl 5, version 38, subversion 2 (v5.38.2) built for x86_64-linux-gnu-thread-multi
(with 44 registered patches, see perl -V for more detail)

iptables v1.8.10 (nf_tables): no command specified

Apr 28 11:55:00.140 [notice] Tor 0.4.8.10 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.1.5, Zlib 1.3, Liblzma 5.4.5, Libzstd 1.5.5 and Glibc 2.37 as libc.

Before I start Nipe:

$ sudo iptables -L
Chain OUTPUT (policy ACCEPT)
target prot opt source destination

Nipe is started:

$ sudo perl nipe.pl start

(chris㉿kali)-[~/nipe]
$ sudo iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
ACCEPT all -- anywhere anywhere state ESTABLISHED
ACCEPT all -- anywhere anywhere owner UID match debian-tor
ACCEPT udp -- anywhere anywhere udp dpt:9061
ACCEPT tcp -- anywhere anywhere tcp dpt:9061
ACCEPT tcp -- anywhere 10.66.0.0/16
ACCEPT all -- anywhere loopback/8
ACCEPT all -- anywhere 192.168.0.0/16
ACCEPT all -- anywhere 172.16.0.0/12
ACCEPT all -- anywhere 10.0.0.0/8
ACCEPT tcp -- anywhere anywhere
REJECT udp -- anywhere anywhere reject-with icmp-port-unreachable
REJECT icmp -- anywhere anywhere reject-with icmp-port-unreachable

Before, several months ago, it was difficult to start Nipe with start but it was working with restart. Now, even restart doesn't work.

$ sudo perl nipe.pl status
[!] ERROR: sorry, it was not possible to establish a connection to the server.`

It is sad that Nipe stopped to work because it is a very good tool.

I hope you can solve the problem.

Thanks.

@htrgouvea
Copy link
Owner

Hey folks,
Recently the Nipe has had many updates. Resolve some bugs that we managed to identify. Can we test again?
Thanks.

@CHFR91
Copy link

CHFR91 commented Jun 25, 2024

It works!!!
Thank you very much.

But, I tried several times before getting a Status: true

If you need some more tests to check, let me know.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants