Hi folks
I'm an ignoramus who had essential help setting up his remote server (ruTorrent 3.2, Debian 6, lighttpd, rtorrent 0.8.9, libTorrent 12.9) which has worked fine for many months. Trying to get my local webui to find ruTorrent on a non-standard port after an overnight break neither Firefox nor IE8 can connect (url not found). I've tried a soft reboot, and ftp works fine and seeding is proceeding as usual, it's just the interface that's screwed. Entering my URL to the standard port 80 opens ruTorrent OK but of course it won't connect to rTorrent (prwesumably because something'd been instrcted to use my nonstandard port). Nothinf in .rtorrent.rc or config.php refers to it, only the sgi port which is working fine.
The initial setup helper isn't available, so any ideas where I might find the configuration info for my webui port?
In very simple & informative terms please, for said ignoramus.
TIA
UPDATE: I learned that OVH monitored the server overnight & found it failed to respond to pings so performed a "hard" reboot. Maybe that caused the problem?
I'm an ignoramus who had essential help setting up his remote server (ruTorrent 3.2, Debian 6, lighttpd, rtorrent 0.8.9, libTorrent 12.9) which has worked fine for many months. Trying to get my local webui to find ruTorrent on a non-standard port after an overnight break neither Firefox nor IE8 can connect (url not found). I've tried a soft reboot, and ftp works fine and seeding is proceeding as usual, it's just the interface that's screwed. Entering my URL to the standard port 80 opens ruTorrent OK but of course it won't connect to rTorrent (prwesumably because something'd been instrcted to use my nonstandard port). Nothinf in .rtorrent.rc or config.php refers to it, only the sgi port which is working fine.
The initial setup helper isn't available, so any ideas where I might find the configuration info for my webui port?
In very simple & informative terms please, for said ignoramus.
TIA
UPDATE: I learned that OVH monitored the server overnight & found it failed to respond to pings so performed a "hard" reboot. Maybe that caused the problem?