/VpnHoodServer/v3.0.423/VpnHoodServer (code=killed, signal=ABRT)

[farzinsb]

after installing vpnhoodserver in linux centos 7 / 8 / 9 it cannot start. I tried using the manual commands I saw that it needs dot net framework in linux so I installed it using this command: dnf -y install dotnet-runtime-6.0 dotnet-sdk-6.0 dotnet-targeting-pack-6.0 dotnet-templates-6.0 dotnet-hostfxr-6.0

but again the service enters the failed state systemctl status VpnHoodServer ● VpnHoodServer.service - VpnHood Server Loaded: loaded (/etc/systemd/system/VpnHoodServer.service; enabled; vendor preset: disabled) Active: activating (auto-restart) (Result: signal) since Thu 2023-09-28 00:26:43 EDT; 9s ago Process: 18384 ExecStart=/opt/VpnHoodServer/v3.0.423/VpnHoodServer (code=killed, signal=ABRT) Main PID: 18384 (code=killed, signal=ABRT)

systemd[1]: VpnHoodServer.service: main process exited, code=killed, status=6/ABRT systemd[1]: Unit VpnHoodServer.service entered failed state. systemd[1]: VpnHoodServer.service failed.

can you help me solve this? i tried in different centos versions all of them failed. even my older ubuntu vps does not work anymore.

I think after update 414 things are getting worse.

[farzinsb]

journalctl -xeu VpnHoodServer
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit VpnHoodServer.service has finished starting up.
--
-- The start-up result is done.
 systemd[1]: VpnHoodServer.service: main process exited, code=killed, status=6/ABRT
 systemd[1]: Unit VpnHoodServer.service entered failed state.
 systemd[1]: VpnHoodServer.service failed.
 systemd[1]: VpnHoodServer.service holdoff time over, scheduling restart.
 systemd[1]: Stopped VpnHood Server.
-- Subject: Unit VpnHoodServer.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit VpnHoodServer.service has finished shutting down.
 systemd[1]: Started VpnHood Server.
-- Subject: Unit VpnHoodServer.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit VpnHoodServer.service has finished starting up.
--
-- The start-up result is done.
 systemd[1]: VpnHoodServer.service: main process exited, code=killed, status=6/ABRT
 systemd[1]: Unit VpnHoodServer.service entered failed state.
 systemd[1]: VpnHoodServer.service failed.
 systemd[1]: VpnHoodServer.service holdoff time over, scheduling restart.
 systemd[1]: Stopped VpnHood Server.

Selinux is disabled , cpu is x86/64 intel xeon.
vps has 2 core , ram 2 gb

[trudyhood]

Hi, Unfortunately, we have only checked the VpnHood server on Ubuntu. However, the recent version uses .NET 7 and does not require .NET runtime, as it is compiled as a standalone.

[farzinsb]

I reinstalled my vps to ubuntu 22 and its working fine. thanks. just the latest win client has errors and wont' start.

[trudyhood]

We have fixed the win client issue. I hope you enjoy it.

[farzinsb]

thanks I updated my server to 3.0.428. can you check one other issue ? I used to change default ports from VpnHood Access Server as I needed port 443 for websites or ssl https services. but in this major recent changes . only default configuration on port 443 is working . and my other older server which had custom port is not functional anymore. even with ubuntu.

[trudyhood]

make sure all your servers have been updated to the recent version. Let me know the error if it doesn't work.

[farzinsb]

all of them are now 3.0.428 . service in linux is active but port custom is not functioning.

lsof -i:3389 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME VpnHoodSe 3110569 root 174u IPv4 15772025 0t0 TCP *****

from my windows client: tcping domain... 3389

Probing ip****:3389/tcp - Port is open - time=1.552ms

[trudyhood]

what is the vpnhood server log?

[farzinsb]

I sent a bug report from win client.
id: 266d946a@20230929T085743-36bc06f6

which linux log file do you need ?

[farzinsb]

root@tr:/opt/VpnHoodServer/storage/logs# vim server.log

"TcpKernelReceiveBufferSize": null,
"TcpConnectTimeout": "00:00:30",
"TcpReuseTimeout": "00:00:40",
"MaxTcpConnectWaitCount": 500,
"MaxTcpChannelCount": 1000,
"NetScanLimit": null,
"NetScanTimeout": null,
"UseUdpProxy2": false

}, "NetFilter": { "IncludeLocalNetwork": false, "PacketCaptureIncludeIpRanges": null, "PacketCaptureExcludeIpRanges": null, "IncludeIpRanges": null, "ExcludeIpRanges": null, "BlockIpV6": false }, "TcpEndPoints": [ "194.*.104:3389" ], "UdpEndPoints": [ "194.**104:42000" ], "UpdateStatusInterval": "00:01:00", "LogAnonymizer": true, "ServerSecret": "*****", "ConfigCode": "54bedb8b-4656-4b88-99cf-ce1daac922c2", "MinCompletionPortThreads": null, "MaxCompletionPortThreads": null }

2023-09-29 12:13:01.5777 | Info | | Server MinWorkerThreads: 2, MinCompletionPortThreads: 30

2023-09-29 12:13:01.5777 | Info | | Server MaxWorkerThreads: 32767, MaxCompletionPortThreads: 65535

2023-09-29 12:13:01.5925 | Info | | Server Starting ServerHost...

2023-09-29 12:13:01.5925 | Info | | Server Start listening on UdpEndPoint: 194...104:42000

2023-09-29 12:13:01.6118 | Info | | Server Start listening on TcpEndPoint: 194...104:3389

2023-09-29 12:13:01.6211 | Info | | Server Server is ready!

[trudyhood]

server looks ok. i will check the clinic log later. Meanwhile make sure there is no network firewall on your server. also make sure your server IP is reachable by clients

[farzinsb]

thanks. tracert to the server from clients is ok. and firewall has allowed that custom port. also I checked with host-tracker with my country agents , and it seems its not filtered by government yet.
does it use other port ranges while sending traffic? but it used to work in this same firewall config for some months. I didn't change firewall rules.

[trudyhood]

Can you give me an access token to your server which does not work? trudy@vpnhood.com

[farzinsb]

I tested with another server on custom port 8443: from client: Probing 94.***.22:8443/tcp - Port is open - time=140.924ms

Pinging grc-d.digik.wiki [94**22] with 32 bytes of data: Reply from 9.22: bytes=32 time=149ms TTL=47

inside linux: lsof -i:8443 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME VpnHoodSe 1033722 root 173u IPv4 3678171 0t0 TCP vm1***:8443 (LISTEN)

 systemctl status VpnHoodServer
● VpnHoodServer.service - VpnHood Server
     Loaded: loaded (/etc/systemd/system/VpnHoodServer.service; enabled; vendor preset: enabled)
     Active: active (running) since Fri 2023-09-29 07:10:24 +0330; 5h 59min ago
   Main PID: 1033722 (VpnHoodServer)
      Tasks: 15 (limit: 2221)
     Memory: 61.7M
        CPU: 1min 9.612s
     CGroup: /system.slice/VpnHoodServer.service
             └─1033722 /opt/VpnHoodServer/v3.0.428/VpnHoodServer

I will email access token to your email now.

[trudyhood]

We could connect to your server. Maybe your client network is too slow. Ask your client to open this page and let me know what they can see. Also, ask them to upgrade their client to the latest version. https://194.x.x.104:3389/

They should get the following error, which is normal.

[farzinsb]

it opens in my chrome . at first it gives error about ssl , then after accepting it , it returns 400 error.

NET::ERR_CERT_AUTHORITY_INVALID and after continuing the page load 400 Bad Request

[farzinsb]

sorry my proxy was active that page loaded. without proxy it gives connection reset and does not open.

[image: image.png]

[image: image.png]

so if the government has filtered the ip by great firewall , how does ping and port checks are working?

also it used to work for some months without getting detected/filtered.

[trudyhood]

Your image has not been loaded. Would you tell your client to temporarily turn off the Windows firewall on his machine to see how it works?

It sounds like something blocks the VpnHood app on your user machine, not the network. It is so strange that he can connect to https://194.x.x.104:3389/ and get that SSL error via the browser but can not do the same via VpnHood client. It happens before any protocol or transfer starts, as it is a completely standard HTTPS web request at this step. See:

Solving such an issue is very difficult as we don't have access to your user network and can't simulate it. Please let us know if someday you are the root of this issue.