Unable to Access Admin Area

[KG60]

SOLVED!

I am having a problem accessing the admin area on my websites created with Processwire on my CWP server (testing server). Everything works fine on my laptop version logging in using localhost/foldername, but when I try using my url to access the server version, the screen just ignores the username & password.
When checking the logs I see the following error:

2025-01-21 11:12:35   admin   https://domainname.co.uk/admin/login/   Successful login for 'admin'
2025-01-21 11:12:35   ?   ?   User 'admin' - Error: Session fingerprint changed (IP address or useragent) (IP: 192.168.178.28)

As this works fine on my laptop with localhost, I would assume that it is something to do with CWP redirecting from my public ip address to my local ip address. I don't have this problem with any Joomla sites I have installed, it appears to be limited to Processwire.

Does anybody know how I can get round this please? Any help would be greatly appreciated.

I am using the following:

ProcessWire 3.0.244
CWP7 Pro
Rocky Linux 8.10 (Green Obsidian)
Apache 2.4.62
PHP 8.3
MariaDB 10.4.34
Nginx - latest version
Varnish - latest version

Edited January 21 by KG60
Now resolved.

[zoeck]

Have you adjusted your URL from the web server in config.php? Does the url in “$config->httpHosts” match?

[KG60]

Thanks for replying. Yes, the url is correct. The actual site works fine, it’s just accessing the admin side that’s the problem. I can make changes using the laptop version, and then upload them to the test server, but that just creates an extra layer.  I’d sooner edit direct only on the test server if possible. 

[DV-JF]

Just guessing because your logs: You could try to add

$config->sessionFingerprint = 2;

to your config.php see https://processwire.com/api/ref/config/#pwapi-methods-session for more info.

 

[KG60]

Thanks for that. After trying a few different options, that's worked, although I've had to set it at = 12; 

Much appreciated.

* After finding that it created another issue with suddenly not being able to login due to the site being supposedly forged, and an unknown error once that was also resolved, I fixed it by changing the initial change to the below:

$config->sessionFingerprint = false;

Edited January 22 by KG60
Extra information due to connected issues