Need help?

Our experts have had an average response time of 11.7 minutes in August 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

How to fix “403 forbidden” error in phppgadmin

by | May 21, 2021

Users often complain that they get a “403 forbidden” message while they try to access phpPgAdmin.

As a part of our Server Management Services, we regularly help our Customers with errors related to phpPgAdmin.

Today, let us discuss the possible reasons and fixes for this error.

What causes “403 forbidden” messages in phpPgAdmin

 phpPgAdmin is a mature web-based administration tool for PostgreSQL. Recently we received a support request from one of our Customers stating that they were receiving a “forbidden” message as shown below while accessing phpPgAdmin.

phppgadmin 403 forbidden

This error generally happens due to some restrictions in the apache configuration file. After the fresh installation of phpPgAdmin, apache2 may not allow us to access phpPgAdmin. Let us see how our Support Engineers fix this error.

How to fix “403 forbidden” messages in phpPgAdmin

Initially, after the installation of phpPgAdmin, we need to follow a series of configuration steps. If they are not followed, we may receive a “Not Found” message while accessing the phpPgAdmin.

For this, we need to configure the Apache server to tell it where to find phpPgAdmin. First, we need to edit /etc/apache2/apache2.conf and add the following line to it.

sudo nano /etc/apache2/apache2.conf

Include /etc/apache2/conf.d/phppgadmin

When you have done this, restart apache:

sudo service apache2 reload

Now, that we have configured Apache, we need to correct the permission. We need to edit the phpPgAdmin file as shown below:

sudo nano /etc/apache2/conf.d/phppgadmin

Here, we need to comment out the following line:

allow from 127.0.0.0/255.0.0.0 ::1/128

Then we need to uncomment the line below it,

allow from all

The file should look like this:

order deny,allow
deny from all
# allow from 127.0.0.0/255.0.0.0 ::1/128
allow from all

Save it out and restart apache again, now try to access phpPgAdmin again. You should be able to see the site now.

[Need any further assistance with PostgreSQL errors? – We’re available 24*7]

Conclusion

In short, the “Forbidden” error triggers while accessing phpPgAdmin when permissions in the phpPgAdmin configuration file are not intact. Today, we saw how our Support Engineers fix this error.

 

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

SEE SERVER ADMIN PLANS

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF