cotonti.com : Can't login when using non-standard port

nicafyl

Di, 29 Mei 2012 00:16:27 -0000

OK, as I don't need this to work (the same install is happily working on port 80), I will just pretend I never saw it. :-)

In a past life I got paid to test software. Ever since I seem to gravitate toward breaking stuff that can't be broken. Good skill -- unless I am just trying to get something done.

Trustmaster

Ma, 28 Mei 2012 20:09:08 -0000

I'll test it on a custom 8092 port and let you know what I find. There may be a bug. Thanks for reporting!

Added 26 minutes later:

I was able to log-in using port 8092. Here is my mainurl from datas/config.php:

$cfg['mainurl'] = 'http://192.168.0.101:8092/cotonti';

I've found a bug when using custom port and $cfg['multihost'] = TRUE, but it's a different thing.

elfrenazo

Ma, 28 Mei 2012 19:42:57 -0000

in data / config.php $cfg['mainurl'] = 'http://coolserv:8092'; what are you wearing like this ?

nicafyl

Ma, 28 Mei 2012 18:54:34 -0000

I didn't configure cookies because I could never log in. But, it turns out that the actual URL and error message was still in a tab on the browser on another system. This is after filling in the login box. I am reasonably sure 'remember me' was not checked.

The URL was: http://coolserv:8092/login.php?a=check

The message in the page being displayed was: An error occured, maybe a wrong URL?

As I said, by just setting up a virtual host on port 80 and changing the URL in config.php, it worked fine.

GHengeveld

Ma, 28 Mei 2012 18:33:15 -0000

Did you configure cookies correctly? Usually login problems are caused by having an incorrect cookie domain or path in Administration panel / Configuration / Security. You can try to login without enabling the 'remember me' checkbox, that will log you in using a session rather than a cookie.

nicafyl

Ma, 28 Mei 2012 17:18:30 -0000

In my first attempt to test out cotonti, I set it up on port 8092 behind Apache. It installed fine but when I attempted to login as the admin I got redirected to a page not found error.

While I have used this "trick" on other software with no problem, I thought it might be my error and moved it to port 80 by just updating the URL in the config file and the Apache sites-available files and it works fine. Because this was Try #1 for me, I didn't save the details of the message but am relatively sure it seemed "sane". That is, had the port number in it.

Clearly this is not a show stopper for anyone but I felt it worth mentioning.

Oops, for to say thing: it is Sienna downloaded this morning from github that this happened with.