You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm facing an issue while setting up Stirling PDF with initial login credentials. There are two ways to run Stirling PDF:
Running as a service: In the /opt/Stirling-PDF/configs/settings.yml file, I’ve set enableLogin: true and added the initial username as test and password as test123. However, when I try to log in, it only accepts admin-stirling and doesn't recognize the initial username and password I configured.
Running manually: When I place the same configuration in the .git directory and run Stirling manually, it correctly accepts the initial username and password as test and test123.
Has anyone encountered this issue where the initial credentials don’t work when running Stirling as a service? How can I solve this problem and ensure that the correct username and password are accepted when running it as a service?
Thanks in advance for any suggestions!
The text was updated successfully, but these errors were encountered:
Hello everyone,
I'm facing an issue while setting up Stirling PDF with initial login credentials. There are two ways to run Stirling PDF:
Running as a service: In the /opt/Stirling-PDF/configs/settings.yml file, I’ve set enableLogin: true and added the initial username as test and password as test123. However, when I try to log in, it only accepts admin-stirling and doesn't recognize the initial username and password I configured.
Running manually: When I place the same configuration in the .git directory and run Stirling manually, it correctly accepts the initial username and password as test and test123.
Has anyone encountered this issue where the initial credentials don’t work when running Stirling as a service? How can I solve this problem and ensure that the correct username and password are accepted when running it as a service?
Thanks in advance for any suggestions!
The text was updated successfully, but these errors were encountered: