+- GetSimple Support Forum (http://get-simple.info/forums)
+-- Forum: GetSimple (http://get-simple.info/forums/forumdisplay.php?fid=3)
+--- Forum: Installation & Setup (http://get-simple.info/forums/forumdisplay.php?fid=5)
+--- Thread: “Warning: Server Setup non-Apache” (GS 3.3.13) (/showthread.php?tid=10464)
“Warning: Server Setup non-Apache” (GS 3.3.13) - GetSimpOwl - 2018-04-29
On the login page (/admin) of my site, a red-box says, “Warning: Server Setup non-Apache”.
I installed GS 3.3.13 on a hosting server with DirectAdmin control panel, using the auto-installer Installatron.
I updated my username and password combination in the Control Panel, but still cannot log in.
How can I fix this?
Thanks.
RE: “Warning: Server Setup non-Apache” (GS 3.3.13) - shawn_a - 2018-04-29
What happens when you try to log in?
RE: “Warning: Server Setup non-Apache” (GS 3.3.13) - GetSimpOwl - 2018-04-30
(2018-04-29, 23:25:38)shawn_a Wrote: What happens when you try to log in?
I get this message: “Error: Login failed. Please double check your Username and Password”.
I again tried with another combination of username and password that I changed in my DirectAdmin control panel, to no avail.
RE: “Warning: Server Setup non-Apache” (GS 3.3.13) - Oleg06 - 2018-04-30
the server is not an apache
RE: “Warning: Server Setup non-Apache” (GS 3.3.13) - Carlos - 2018-04-30
The non apache warning can be removed and is not related to your problem, I think.
Do you know the username for your GetSimple site? If so, you can click on "Forgot your password?" and you'll received a new one.
I suppose that your DirectAdmin username and password is not related to GS, but I don't know how that Installatron script works. If you cannot solve this, perhaps you should contact your host.
RE: “Warning: Server Setup non-Apache” (GS 3.3.13) - Tyblitz - 2019-03-26
Here's the installatron service: https://installatron.com/getsimple/install (I think it's commonly integrated into cPanel providers).
Btw, I once successfully installed GS on an Nginx server, but it did take some tweaking (essentially rewriting htaccess rules in Nginx-compatible format)