Remote Login unable to login [SOLVED]

I get the error "unable to login please check your password and try again" when trying to remote in using my website linked to my server setup through Apache2. I do get the Serviio login however but when entering password it comes back invalid. I am able to login with (same password) fromhttp://Localhost:32424/mediabrowser and http://server-ip:32424/mediabrowser both work (I can login and password is accepted). Also tried outside my LAN at a different location and again I get the login screen but once I enter password if says unable to login.

Not sure if it is Apache because like I said I see the serviio login screen. I am running Ubuntu and Apache2 using a ProxyPass (which does work for other applications sabnzbd, sickbeard, and couchpotato). Here's a snippet of my Apache2 httpd.conf file

  Code:

<Location /mediabrowser>
order deny,allow
deny from all
allow from all
ProxyPass http://localhost:23424/mediabrowser
ProxyPassReverse http://localhost:23424/mediabrowser
</Location>

I can't seem to get anything useful from the serviio log files

  Code:

2012-07-26 18:26:12,407 DEBUG [DiscoveryAdvertisementNotifier] Multicasting SSDP alive using interface eth0 (eth0) and address 192.168.1.110, timeout = 0
2012-07-26 18:26:12,408 DEBUG [DiscoveryAdvertisementNotifier] Sending 6 'alive' messages describing device 00f06443-398c-3d99-ae1a-d31c171b4221
2012-07-26 18:26:14,210 DEBUG [DiscoveryAdvertisementNotifier] Will advertise again in 00:00:37
2012-07-26 18:26:19,064 DEBUG [FeedUpdaterThread] Checking for new and expired online resources
2012-07-26 18:26:19,064 DEBUG [OnlineRepositoryDAOImpl] Reading all OnlineRepositories
2012-07-26 18:26:19,064 DEBUG [OnlineRepositoryDAOImpl] Reading an OnlineRepository (id = 1)
2012-07-26 18:26:19,070 DEBUG [OnlineRepositoryDAOImpl] Reading an OnlineRepository (id = 2)
2012-07-26 18:26:19,084 DEBUG [OnlineRepositoryDAOImpl] Reading an OnlineRepository (id = 3)
2012-07-26 18:26:51,899 DEBUG [DiscoveryAdvertisementNotifier] Multicasting SSDP alive using interface eth0 (eth0) and address 192.168.1.110, timeout = 0
2012-07-26 18:26:51,900 DEBUG [DiscoveryAdvertisementNotifier] Sending 6 'alive' messages describing device 00f06443-398c-3d99-ae1a-d31c171b4221
2012-07-26 18:26:53,702 DEBUG [DiscoveryAdvertisementNotifier] Will advertise again in 00:00:55
2012-07-26 18:27:19,094 DEBUG [FeedUpdaterThread] Checking for new and expired online resources
2012-07-26 18:27:19,094 DEBUG [OnlineRepositoryDAOImpl] Reading all OnlineRepositories
2012-07-26 18:27:19,094 DEBUG [OnlineRepositoryDAOImpl] Reading an OnlineRepository (id = 1)
2012-07-26 18:27:19,102 DEBUG [OnlineRepositoryDAOImpl] Reading an OnlineRepository (id = 2)
2012-07-26 18:27:19,115 DEBUG [OnlineRepositoryDAOImpl] Reading an OnlineRepository (id = 3)
2012-07-26 18:27:49,358 DEBUG [DiscoveryAdvertisementNotifier] Multicasting SSDP alive using interface eth0 (eth0) and address 192.168.1.110, timeout = 0
2012-07-26 18:27:49,359 DEBUG [DiscoveryAdvertisementNotifier] Sending 6 'alive' messages describing device 00f06443-398c-3d99-ae1a-d31c171b4221
2012-07-26 18:27:51,161 DEBUG [DiscoveryAdvertisementNotifier] Will advertise again in 00:00:49
2012-07-26 18:28:19,185 DEBUG [FeedUpdaterThread] Checking for new and expired online resources
2012-07-26 18:28:19,185 DEBUG [OnlineRepositoryDAOImpl] Reading all OnlineRepositories
2012-07-26 18:28:19,186 DEBUG [OnlineRepositoryDAOImpl] Reading an OnlineRepository (id = 1)
2012-07-26 18:28:19,191 DEBUG [OnlineRepositoryDAOImpl] Reading an OnlineRepository (id = 2)
2012-07-26 18:28:19,201 DEBUG [OnlineRepositoryDAOImpl] Reading an OnlineRepository (id = 3)


Does anybody have any ideas? Thanks,

[will]

Can you follow this link http://wiki.serviio.org/doku.php?id=detail_logging but instead turn the org.rest part in your log config file to DEBUG

That will at least print out the communication logs.

Will thanks for the reply. I did what you said and attached is the log file.

  Code:

Framework/2.0.10   -
2012-07-27 20:58:05,401 INFO  [LogService] 2012-07-27   20:58:05   127.0.0.1   -   -   23423   GET   /rest/library-status   -   200   -   0   0   http://localhost:23423   Restlet-Framework/2.0.10   -
2012-07-27 20:58:08,006 INFO  [LogService] 2012-07-27   20:58:08   127.0.0.1   -   -   23424   GET   /mediabrowser   -   307   0   0   1   http://localhost:23424   Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20100101 Firefox/14.0.1   http://serviio.BLANK.net/
2012-07-27 20:58:10,506 INFO  [LogService] 2012-07-27   20:58:10   127.0.0.1   -   -   23423   GET   /rest/library-status   -   200   -   0   0   http://localhost:23423   Restlet-Framework/2.0.10   -
2012-07-27 20:58:15,610 INFO  [LogService] 2012-07-27   20:58:15   127.0.0.1   -   -   23423   GET   /rest/library-status   -   200   -   0   1   http://localhost:23423   Restlet-Framework/2.0.10   -
2012-07-27 20:58:20,714 INFO  [LogService] 2012-07-27   20:58:20   127.0.0.1   -   -   23423   GET   /rest/library-status   -   200   -   0   1   http://localhost:23423   Restlet-Framework/2.0.10   -
2012-07-27 20:58:25,818 INFO  [LogService] 2012-07-27   20:58:25   127.0.0.1   -   -   23423   GET   /rest/library-status   -   200   -   0   1   http://localhost:23423   Restlet-Framework/2.0.10   -


It looks like going to port 23423 is normal even when I locally login. However, I'm wondering if this is throwing off the proxypass in apache.

EDIT: I looked into it a little more comparing local login and remote and it looks like in the remote login the authToken is not being sent. After doing some research I am assuming this probably relates to the proxypass not passing on the authToken from the server to the browser or vice versa. However, I have no idea how to fix it.

[will]

23423 is the console running in the background. Can you exist it and post a local and remote login attempt.

There is nothing special about the login. The client does a request with the hashed details, and gets the token in the response. The token is then appended to the end of urls.

I'll have a think/try your setup on my Linux box this weekend. Anything special you did to set it up?

I've looked at the apache logs and when I enter a password remotely into serviio mediabrowser I get the error "File does not exist /var/www/cds referer http://serviio...

[will]

Ah, ok, cds is the Content Delivery System API that the mediabrowser and other apps use to access content. Try adding a rule for /cds that points to ip:23424/cds

Thanks Will that did the trick. Just incase anybody wants to know how to setup the remote login using Apache2 with a proxypass your httpd.conf file needs to contain the following:

[quote][/quote]

  Code:

<Location /mediabrowser>
order deny,allow
deny from all
allow from all
ProxyPass http://localhost:23424/mediabrowser
ProxyPassReverse http://localhost:23424/mediabrowser
</Location>

<Location /cds>
order deny,allow
deny from all
allow from all
ProxyPass http://localhost:23424/cds
ProxyPassReverse http://localhost:23424/cds
</Location>

Will everything seems to be working now. I can now login to serviio with the address http://mydomain/mediabrowser

I have not fully tested every functionality is there anything else I need to be aware of that lives outside of the mediabrowser folder like cds did? I know very little about coding but I would recommend if possible keeping everything in mediabrowser to prevent problems like these.

However, thank you so much for the quick responses and the help. I'm excited to become a pro user.

[will]

Glad you got it working. There is nothing outside those two, the reason for the seperatation is that /mediabrowser is the webapp front end, and /cds is the actual API used to access the content which media browser and ServiiGo uses (and hopefully more apps in the future). If you did use ServiiGo it wouldn't be aware of your proxypath so you would need port 23424 open.

I'd like to get this working via an SSL Reverse Proxy on Apache. I can get it to come up with the login screen on a different port (23425) but as mentioned here, as soon I try to login I get wrong password every time.

If I disable SSL and change my port 23425 to HTTP, it'll work just fine. So the instructions here are sound but as soon as you try to reverse proxy it with SSL it doesn't work.

It's not the end of the world, I just like a bit more security is all

[will]

I'd like to get this working via an SSL Reverse Proxy on Apache. I can get it to come up with the login screen on a different port (23425) but as mentioned here, as soon I try to login I get wrong password every time.

If I disable SSL and change my port 23425 to HTTP, it'll work just fine. So the instructions here are sound but as soon as you try to reverse proxy it with SSL it doesn't work.

It's not the end of the world, I just like a bit more security is all

Just saw your post, next time make a new thread. Did you get it working? I don't see why wrapping it in SSL should cause a problem, the login process is pretty standard stuff.