hiddify / Hiddify-Manager

Multi-user anti-filtering panel, with an effortless installation and supporting more than 20 protocols to circumvent filtering plus the telegram proxy.
https://hiddify.com
GNU General Public License v3.0
6.07k stars 710 forks source link

WARP & sysctl errors #4270

Open crxssrazr93 opened 2 months ago

crxssrazr93 commented 2 months ago

Here's what my service status looks like:

- Services Status:
    hiddify-cli                   active
    hiddify-redis                 active
    hiddify-ssh-liberty-bridge    active
    hiddify-haproxy               active
    hiddify-panel                 active
    hiddify-nginx                 active
    hiddify-singbox               active
    hiddify-xray                  active
    wg-quick@warp                 failed
    mtproto-proxy                 active

As you can see, it shows wg-quick@warp as failed.

Further inspection reveals this:

Jul 10 22:36:06 hiddify-sg systemd[1]: Starting WireGuard via wg-quick(8) for WARP...
░░ Subject: A start job for unit wg-quick@WARP.service has begun execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit wg-quick@WARP.service has begun execution.
░░
░░ The job identifier is 97590.
Jul 10 22:36:06 hiddify-sg wg-quick[107206]: wg-quick: `/etc/wireguard/WARP.conf' does not exist
Jul 10 22:36:06 hiddify-sg systemd[1]: wg-quick@WARP.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit wg-quick@WARP.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Jul 10 22:36:06 hiddify-sg systemd[1]: wg-quick@WARP.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit wg-quick@WARP.service has entered the 'failed' state with result 'exit-code'.
Jul 10 22:36:06 hiddify-sg systemd[1]: Failed to start WireGuard via wg-quick(8) for WARP.
░░ Subject: A start job for unit wg-quick@WARP.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit wg-quick@WARP.service has finished with a failure.
░░
░░ The job identifier is 97590 and the job result is failed.

On another note, I also get these errors;

sysctl: setting key "net.ipv4.conf.all.accept_source_route": Invalid argument
sysctl: setting key "net.ipv4.conf.all.promote_secondaries": Invalid argument

I have tried reinstalling to no avail.

Sajjad-Arjmand commented 1 month ago

same here:

85####Installing...####Wireguard####

===install.sh other/wireguard sysctl: setting key "net.ipv4.conf.all.accept_source_route": Invalid argument sysctl: setting key "net.ipv4.conf.all.promote_secondaries": Invalid argument ===run.sh other/wireguard

crxssrazr93 commented 1 month ago

I made a backup, and did a restore keeping only user information. The rest I reconfigured from scratch and it has been fine.

I was still unable to address the sysctl errors.