Accessing web interface multiple users

Feel free to talk about anything and everything in this board.
Post Reply
lmartinl
Newbie
Newbie
Posts: 2
Joined: January 10th, 2012, 9:36 am

Accessing web interface multiple users

Post by lmartinl »

Hi there,

Currently I'm having troubles with the web interface of sabnzbd. I couldn't find anything about it, but is it build to be used/viewed by multiple users at the same time?

When i try to log into the server from a different pc, multiple problems occur.
Sometimes I can't get a server response
Sometimes I do get in, but the download speed drops from 20MB/s to like 200 KB/s
Sometimes everything works perfectly

Also, what is the effect if the pc that's running Sabnzb goes to the windows loginscreen (change user screen; Windows+L)?

Latest version of sabnzbd, smple-black skin.
Windows 7, 64 bits

Best regards,
Martin
User avatar
shypike
Administrator
Administrator
Posts: 19773
Joined: January 18th, 2008, 12:49 pm

Re: Accessing web interface multiple users

Post by shypike »

SABnzbd is single user, but can support multiple sessions.
These sessions obviously influence each other.
Having many sessions open in combination with a high refresh rate
will mean a significant load on SABnzbd.
If you have many sessions, lower the refresh rate.
SABnzbd will keep running as long as the user that started it doesn't log out.
So "fast user switching" should work.
Although in such a case you should consider running it as a Windows Service.
(See our Wiki).
Marcoevich
Jr. Member
Jr. Member
Posts: 54
Joined: January 1st, 2012, 2:35 pm

Re: Accessing web interface multiple users

Post by Marcoevich »

Activating the logon screen doesn't have any effect on SABnzbd. My pc is alsways locked if I'm not at home and that works flawless ;)
lmartinl
Newbie
Newbie
Posts: 2
Joined: January 10th, 2012, 9:36 am

Re: Accessing web interface multiple users

Post by lmartinl »

Thanks for the replies. Suddenly everything works fine. I guess the problems occured because of 100 percent cpu usage on par2 repairing, which probably withheld the server from accepting incoming connections for the web interface
Post Reply