• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

Question Forbidden access to adminer

HairLoss

New Pleskian
Hi, I am trying to install adminer, a mysql web interface, so that I can administer all my databases from one logon and don't get timed out so often. However, though I have followed some simple online instructions I get the 403 Forbidden access message when I try to fire up adminer.

Adminer was installed to usr/share/adminer and a configuration file was created at /etc/httpd/conf.d/adminer.conf as follows;

Alias /adminer "/usr/share/adminer"
<Directory "/usr/share/adminer">
AllowOverride All
Options FollowSymlinks
Order deny,allow
Deny from all
Allow from [my home IP address]
</Directory>

I have tried calling the program with my server IP address and a domain registered on the VPS but with no success.

I have read that there may be conflicting apache rules in the system httpd.conf file but I have only been able to find such files associated with specific domains.

Does anyone have any suggestions that might get adminer working?

Thanks
 
First thing that comes into my mind is whether you are using Nginx as a proxy. That can mean that you need to open the website on port 7080, e.g. www.mydomain.com:7080 to reach Apache. Second thought is that the home IP address might be wrong. And have you checked that httpd service was restarted after the new configuration file was installed? Really, many different things can influence the behavior.
 
Back
Top