Login Problem After Upgrade to 1.2.11

[patrickr]

After upgrading to 1.2.11 I found that we couldn't log in to Cacti.
It appears that the cause it being referred to a bug in https://github.com/Cacti/cacti/issues/3436.

The problem is that I have installed a new VM running CentOS 7 and can confirm that this isn't the issue. While I am able to log in and complete the initial install as well as log in and log out, once I close my browser, I am no longer able to log back into the system.

I have put our original system back in place as it's poller at least seems to be gathering data and sending the daily reports we need. We just can't log in to manage the graphs or system.

Any help would be appreciated.

[TheWitness]

Edit the config.php and comment out $cacti_cookie_domain, until you have a valid Cookie domain set.

[patrickr]

Edit the config.php and comment out $cacti_cookie_domain, until you have a valid Cookie domain set.

I have done that. On multiple different machines. Everything works until I close the browser and try to go back in. Something else appears to be broken.

[TheWitness]

Well, other common things:

1) Unable to write to /var/lib/php/session
2) Full File System in /var/lib/php/session
3) Using session cookies (keep me logged in) and switching between http and https (I've seen this, but was never able to reproduce)

[TheWitness]

I've confirmed 3), but it's to be expected. If you start a session using https, and then switch to httpd, logout, and then attempt to login again, it will not work until you close your browser and go in as http again. This is due to an expired cookie already having been setup as secure, which is incompatible with http handler on the server side.

[patrickr]

I've confirmed 3), but it's to be expected. If you start a session using https, and then switch to httpd, logout, and then attempt to login again, it will not work until you close your browser and go in as http again. This is due to an expired cookie already having been setup as secure, which is incompatible with http handler on the server side.

We don't switch between http and https. The system is forwarding all http traffic to https.

[patrickr]

I've confirmed 3), but it's to be expected. If you start a session using https, and then switch to httpd, logout, and then attempt to login again, it will not work until you close your browser and go in as http again. This is due to an expired cookie already having been setup as secure, which is incompatible with http handler on the server side.

I created a new server yesterday that is running CentOS 7, PHP 7.3 and MariaDB 10.4.
After installing LAMP and Cacti, I was able to log in and out multiple times using local and LDAP authentication. The only time the login didn't work was if I used a saved login on Firefox.
This morning I attempted to login and am getting the same login loop as on our old server. I don't understand why it worked yesterday but doesn't work this morning.
THIS IS FRUSTRATING AND NEEDS TO BE FIXED!!

[netniV]

The cookie domain issue is resolved and will be in this weekends release. However, your issues seem to go beyond that so maybe usie the developer tools in your browser to verify the cookie states and ensure they match your site details. It is likely that your session is keeping you running and once that expires, cacti will attempt to read the cookie.

[patrickr]

The cookie domain issue is resolved and will be in this weekends release. However, your issues seem to go beyond that so maybe usie the developer tools in your browser to verify the cookie states and ensure they match your site details. It is likely that your session is keeping you running and once that expires, cacti will attempt to read the cookie.

I don't believe so. The cookie issue appears to be more than just commenting out a line in the configuration. When I am able to log into our console, if I close the page and open another, I am being asked to login again.

I am hopeful that the new release will help resolve these issues.

[TheWitness]

I don't see this issue, but I'm also using sessions cookies (keep me signed in) feature too.

[patrickr]

I don't use this issue, but I'm also using sessions cookies (keep me signed in) feature too.

Even if I click on "Keep me logged in", I am still prompted to login again after closing the browser window.

[TheWitness]

I don't know what to say. When you figure it out though share with others.