Not possible to install at CentOS 7 machines #90
Comments
|
Im having the same issue |
|
Add one to the number of people having this issue. |
|
Fresh install on AWS using Amazon Linux 2 and I have the same issue. So this is not just CentOS 7, but possibly anything based on RedHat Enterprise 7. |
|
fwiw, one more facing the same limitation. |
|
Exact same issue for me, with PHP 7.3 on CentOS 7. Occurs when downloading the tgz file from pdnsmanager.org and when building the project from source cloned from github. |
|
Anyone fixed this issue ? |
|
The code called for setup is in backend/controllers/Setup.php you can enter debug messages here and check where it fails. I have no experience in cent os therefore it is difficult to check that and it would take me much time. If you have clues please ask again. |
|
Can someone of you check if the change suggested by @medea61 in loewexy/pdns-manager-website#9 solves the problem for you. I just tested it on my Ubuntu setups and it works fine there. |
|
Looks like the setup works fine after loewexy/pdns-manager-website#9. Will do some more testing and will let you know |
|
loewexy/pdns-manager-website#9 worked for me too with php 7.4 |
It seems not possible to install PDNS Manager 2.0.1 at CentOS 7 machines.
All requirements are met (PHP 7.1.26, mysqlnd, APCU), the files are owned by the webserver user, config is writable.
However, wenn /setup is called and all data is inserted into the fields and sent to /api/v1/setup, nothing happens. The database won't be set up, no files are written. The screen switches to the login screen and you can login with any data, no matter what you write into the user/password fields. You see an empty dashboard where you can't do anything.
There are no error messages anywhere. Not in the browser console, not in the PHP log, not in any log files. The Webserver access log shows a regular 200 response.
I have no clue what is going on...
It looks like the slim database connection is broken and everything fails silently.
The text was updated successfully, but these errors were encountered: