![]() ![]() ![]() The nf I mentioned, was just because I thought you used deluge-console to connect to VPS from your laptop, and since deluge-console has bug adding new host so need done that way instead, so not relevant, but adds regardless just in case relevant somehow anyway, and since you also asked: Also, maybe try IP instead of URL, though should work with URL but regardless. foo:bar:10 under VPS /var/lib/deluge/.config/deluge/auth and connecting to that same user/password/port/url from laptop. As you said, remote connections enabled and having e.g. Does it say online at-least in connection-manager? Does it lists as having that port open from outside from other means like ? VPS deluged I mean. I'm sorry I don't know why cannot connect to seedbox from GTK-UI, unless it's the deluged daemon now acting up, but you had this issue since start though. as quick hack 'sudo -u deluge deluge-console'. If running deluge-console on your VPS to check deluged, then it's normal it states password not match if just pressing return to connect default localhost:58846, but works if using e.g. Initially I thought you meant GTK-UI with the "lite client" mention, but then when mentioning console-UI I thought maybe that was said lite-client.Īnyway, for the issue with deluged on seedbox, then I don't know if can reboot such, but I would stop service, run just in case 'sudo pkill -9 deluged'(in case local deluged somehow running, blocking systemd's) and delete /var/lib/deluge/.config/deluge if not having anything important(or rename it to end in bak, so gets regenerated and have backup), then start service again from systemd and hopefully works fresh. ![]() Main PID: 163292 (code=exited, status=1/FAILURE)Īug 25 12:42:52 kyats5000 systemd: rvice: Failed with result 'exit-code'.Īug 25 12:42:52 kyats5000 systemd: rvice: Consumed 1.256s CPU time.Īug 25 12:42:52 kyats5000 systemd: rvice: Scheduled restart job, restart counter is at 5.Īug 25 12:42:52 kyats5000 systemd: Stopped Deluge Bittorrent Client Daemon.Īug 25 12:42:52 kyats5000 systemd: rvice: Start request repeated too quickly.Īug 25 12:42:52 kyats5000 systemd: Failed to start Deluge Bittorrent Client Daemon. Process: 163292 ExecStart=/usr/bin/deluged -d (code=exited, status=1/FAILURE) Loaded: loaded (/etc/systemd/system/rvice enabled vendor preset: enabled)Īctive: failed (Result: exit-code) since Thu 12:42:52 UTC 2s ago × rvice - Deluge Bittorrent Client Daemon I am now facing what appears to be a separate issue. My ~/.config/deluge/auth has a seperate user:password:10 format which is the one I am attempting to use from the 'lite client' in connection manager. This is great and secure, but does not suit my needs as I would prefer to use the client to make magnet links work right away.Īny advice on how to get this resolved? I have remote access enabled and I have restarted deluge so I know I am good there. My presumption right now is that the actual deluge server (2.1.1.) is running on localhost, which deluge-web is configured to point to internally while it serves http get requests externally. can it be remote? If so, how can i run deluge to connect via my.:58846 My deluge-console correctly states the host is running deluged on 127.0.0.1:58846. However, I want to connect via the lite client remotely, as in, from my local machine which is in a faraway location from the host deluge. ![]() Web-deluge is working flawlessly, as I am able to connect via http in a browser to my-domain:8112, input the web password, and I'm fine. I have a VPS/KVM-hosted ubuntu22.0.4 machine with a deluge server running (deluged service active) on the default port. I have a silly question about connecting to my deluge server via the lite client on my remote machine. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |