pictory admin password not working

[dirk]

Hello PIify_Amanda,
currently we are trying to reproduce the error.
Therefore we cannot say that the "dist-upgrade" is directly involved with the error.

But meanwhile we want to provide you with those helpful thoughts
1. Clear the browser cache
https://www.digitaltrends.com/computing ... ser-cache/

2. reinstall piCtory via

Code: Select all

sudo apt-get install --reinstall pictory

3. reinstall Webstatus via

Code: Select all

 sudo apt-get install --reinstall webstatus 

Hope this helps.

[dirk]

Hello PIify_Amanda or Carl-Johan,
could you please check
a)if the file exists "/var/www/data/login.json"
b) and the size is > 0 bytes?

you may run this command (here the size is 65 bytes)

Code: Select all

ls -l /var/www/data/login.json
-rw-r--r-- 1 www-data www-data 65 Jan  1 05:03 /var/www/data/login.json

if not then please create the file by using the following commands

Code: Select all

sudo echo -n '{"username":"admin","ownPW":"","lastLogin":"1970-01-01 03:06:06"}' | sudo tee /var/www/data/login.json > /dev/null
sudo chown www-data:www-data /var/www/data/login.json

Then you should be able to login again on the Webstatus using the default credentials.
User "admin" and the passwod from "piSerial" command...

[PIify_Amanda]

Thank you Dirk.

ls -lah
-rw-rw---- 1 www-data www-data 46 Jun 3 22:08 login.json

sudo cat login.json
{"username":"admin","ownPW":"","lastLogin":""}

Adding a date in "lastLogin" did not change behaviour.

Cheerio

[dirk]

Hello PIify_Amanda ,
could you please check thata the output of piSerial is valid?
Please don't post the output here public for security reasons.
Please just test if the default password is displayed.

If the password is not displayed then the I2C bus may be
the root cause of the error...

[LEOMENA]

I can confirm.. That happened to me as well, although I ran a sudo apt-get update and then sudo apt-get upgrade, then I started to have the same problem: I cannot access Pictory, and piSerial tells me that the password has not changed.!!!

[LEOMENA]

Dirk,
Have you figured out a way to fix this? If so, please send instructions on how to regain control via Pictory GUI.

Please note that I can access Pictory from inside my Revpi. by opening a browser and using the hostname of my Revpi. But I cannot do it from my Laptop anymore.

[kjkoster]

Dear Leomena,

Sorry to put my nose into a thread that I cannot reproduce and speak about a problem that I do not have, but...

Just to check: You state that you can use the browser running on the UI of the RevPi to access pictory, but from your laptop via the network you cannot. Correct?

If that is the case, it sounds to me like something else than the password. It sounds to me that your browser and the pictory server-side component disagree about your user session. Perhaps your browser does not accept or retain the session cookies? Some plugings or policies forbid that.

If you have a heavily locked-down laptop from your work, try the same with a normal machine that does not have too many restrictions (just to narrow down the problem). If your phone is on the right network, try using the browser on your phone and see what happens.

Also, what is between your laptop and the RevPi, network-wise? There could be a proxy server scrubbing your network traffic a bit too vigorously. To test this, you could try to patch you laptop into an ethernet port on your pi directly (again, just to narrow down the problem).

Maybe, just maybe, this is related to the fact that the newer pictory redirects to another port after login?

If you cannot access pictory even locally, then I don't know what could be the problem.

Kees Jan

[nicolaiB]

Hi Kees,

thanks for your great support. I couldn't have said it better

Nicolai

[LEOMENA]

Kees and Nikolai,
Thanks so much for prompt response!!. BTW, No nosing at all, I am happy that I could get support from you.. !!

I Will try your suggestions and reply asap.

Thanks!!

[LEOMENA]

Kees and Nikolai,

As it turns out, Kees' idea of using my phone nailed it! as I was able notice that for the second time after I did a ("sudo apt-get update" + "sudo apt-get upgrade") I had seen the attached IMPORTANT NOTICE, that I totally disregarded the first time (I think I did it in auto mode, but at least I remembered!!).
So I did the regular CTRL - F5 cache clearing and voila! Problem solved..
Sometimes, when you're in auto you just make such silly mistakes..
I hope this is also helpful for others..

Anyways, Thank you so much for the help!!!