Search…

X3 Photo Gallery Support Forums

Search…
 
PeterR
Topic Author
Posts: 3
Joined: 10 May 2019, 20:22

Help with install on local FreeBSD server - HTTP 500 error when trying to access panel

11 May 2019, 04:51

Hi,

I'm trying to install X3 on a machine running FreeBSD (11.2, w/ Apache 2.4 / PhP 7.1) in my local network.
I must admit I barely know enough about this stuff to be dangerous, but somehow I managed to install and make the diagnostics happy:
x3login.JPG
x3login.JPG (25.6 KiB) Viewed 3314 times
and get to the login screen:
x3login.JPG
x3login.JPG (25.6 KiB) Viewed 3314 times
But hitting login results in a HTTP500 error.
Code
Access log:

192.168.0.234 - - [11/May/2019:02:18:29 +0200] "GET /x3/ HTTP/1.1" 200 1051
192.168.0.234 - - [11/May/2019:02:18:29 +0200] "GET /x3/app/public/css/diagnostics.css?v=3.27.6 HTTP/1.1" 200 2862
192.168.0.73 - - [11/May/2019:02:18:29 +0200] "GET /x3/config/readme.txt HTTP/1.0" 403 229
192.168.0.73 - - [11/May/2019:02:18:29 +0200] "GET /x3/render/w/custom/favicon/favicon.png HTTP/1.0" 200 940
192.168.0.234 - - [11/May/2019:02:18:29 +0200] "POST /x3/ HTTP/1.1" 200 734
192.168.0.234 - - [11/May/2019:02:18:29 +0200] "GET /favicon.ico HTTP/1.1" 404 209
192.168.0.234 - - [11/May/2019:02:18:30 +0200] "GET /x3/panel/ HTTP/1.1" 200 6553
192.168.0.234 - - [11/May/2019:02:18:30 +0200] "GET /x3/panel/filemanager_css/x3.panel.css?v=3.27.6 HTTP/1.1" 200 61605
192.168.0.234 - - [11/May/2019:02:18:38 +0200] "POST /x3/panel/login.php HTTP/1.1" 500 -


Code
Error log:

[Sat May 11 02:18:29.050736 2019] [authz_core:error] [pid 43267] [client 192.168.0.73:36872] AH01630: client denied by server configuration: /usr/local/www/apache24/data/x3/config/readme.txt
I'm sure it's something obvious, but I'm a little out of my depth here. Any ideas would be greatly appreciated...

Thanks a lot,
Peter
Attachments
x3diag.JPG
x3diag.JPG (33.32 KiB) Viewed 3314 times
 
User avatar
mjau-mjau
X3 Wizard
Posts: 13993
Joined: 30 Sep 2006, 03:37

Re: Help with install on local FreeBSD server - HTTP 500 error when trying to access panel

11 May 2019, 09:17

Unfortunately, it's difficult for me to diagnose this from here. Are there some firewall rules? Perhaps your server has blocked ini_set() command? Can you try to disable/remove the .htaccess file? Could it be something else in your custom server config? Is the PHP compiled as standard with all extensions I wonder? Do you have full diagnostics? Is there a public url you could give so I can take a closer look?

As for the access log, that is entirely normal ... I just see the expected files being accessed.

Code
Error log:
[Sat May 11 02:18:29.050736 2019] [authz_core:error] [pid 43267] [client 192.168.0.73:36872] AH01630: client denied by server configuration: /usr/local/www/apache24/data/x3/config/readme.txt
Error log could have been helpful, but the above error is not related to the panel (as you can see, it's not even in the /panel/ path). The above request for /config/readme.txt is triggered by X3 diagnostics, making sure that the X3 /config/ directory is NOT readable. So in this case, since the request is successfully being blocked (by authz_core), the above is correct and expected. Nothing to do with panel login though  :confused:

Do you have some kinda PHP error log somewhere?
 
PeterR
Topic Author
Posts: 3
Joined: 10 May 2019, 20:22

Re: Help with install on local FreeBSD server - HTTP 500 error when trying to access panel

11 May 2019, 12:53

Ah, one step further. The hint that that was expected behaviour and I should start looking for PHP errors was actually really helpful.
Code
[11-May-2019 16:38:42 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function mcrypt_encrypt() in /usr/local/www/apache24/data/x3/panel/filemanager_core.php:219
pkg install php71-mcrypt got me into the panel now  :wink:
I'm sure I'm going stumble over my next blunder in no time, but thanks so much for now  :slight_smile:
 
PeterR
Topic Author
Posts: 3
Joined: 10 May 2019, 20:22

Re: Help with install on local FreeBSD server - HTTP 500 error when trying to access panel

12 May 2019, 12:14

  Had to install still a few further extensions, but works fine now. Thanks again  :slight_smile: