XRay not working on Linux

[indx0]

Describe the bug
Xray VPN protocol is not working on linux. Connetion is successfull, but you cannot access any sites.

To Reproduce
Steps to reproduce the behavior:

1. Install XRay on your server
2. Connect to the VPN
3. Try to access any website with a web browser
4. See error

Expected behavior
VPN works as expected and sites are accessible.

Log files

AmneziaVPN.log
AmneziaVPN-service.log

Screenshots

Desktop:

• OS: Fedora Linux KDE
• Version 41

Server:

• OS: Ubuntu 24.04

Additional context
Also, the problem persists after disconnecting from VPN. Only thing that helps - connecting to another protocol (for example, AmneziaWG) and then disconnecting from it. After that sites are accessible again.

The problem is clearly with the client, because the same bug happens, when using Xray configs not from amnezia, but from other services.

[outspace]

Something with DNS setup.

Please append logs from journalctl -xeu systemd-resolved.service

[indx0]

мар 01 22:21:56 thinkpad systemd[1]: Started systemd-resolved.service - Network Name Resolution.
░░ Subject: A start job for unit systemd-resolved.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit systemd-resolved.service has finished successfully.
░░ 
░░ The job identifier is 17706.
indx@thinkpad:~$ journalctl -xeu systemd-resolved.service
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A stop job for unit systemd-resolved.service has begun execution.
░░ 
░░ The job identifier is 19079.
мар 01 22:22:41 thinkpad systemd[1]: systemd-resolved.service: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit systemd-resolved.service has successfully entered the 'dead' state.
мар 01 22:22:41 thinkpad systemd[1]: Stopped systemd-resolved.service - Network Name Resolution.
░░ Subject: A stop job for unit systemd-resolved.service has finished
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A stop job for unit systemd-resolved.service has finished.
░░ 
░░ The job identifier is 19079 and the job result is done.
мар 01 22:22:41 thinkpad systemd[1]: systemd-resolved.service: Start request repeated too quickly.
мар 01 22:22:41 thinkpad systemd[1]: systemd-resolved.service: Failed with result 'start-limit-hit'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit systemd-resolved.service has entered the 'failed' state with result 'start-limit-hit'.
мар 01 22:22:41 thinkpad systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution.
░░ Subject: A start job for unit systemd-resolved.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit systemd-resolved.service has finished with a failure.
░░ 
░░ The job identifier is 19079 and the job result is failed.
мар 01 22:22:41 thinkpad systemd[1]: systemd-resolved.service: Start request repeated too quickly.
мар 01 22:22:41 thinkpad systemd[1]: systemd-resolved.service: Failed with result 'start-limit-hit'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit systemd-resolved.service has entered the 'failed' state with result 'start-limit-hit'.
мар 01 22:22:41 thinkpad systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution.
░░ Subject: A start job for unit systemd-resolved.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit systemd-resolved.service has finished with a failure.
░░ 
░░ The job identifier is 19098 and the job result is failed.