Articles in this section

See more

Unable to log in to Plesk Obsidian: Error: Access for administrator from address '127.0.0.1' is restricted in accordance with IP Access restriction policy currently applied.

Avatar
Kuzma Ivanov
Updated
Follow
kb: bug ABT: Group A Plesk Obsidian for Linux

Applicable to:

  • Plesk Obsidian for Linux

Symptoms

Unable to log in to Plesk Obsidian:

PLESK_ERROR: Error: Access for administrator from address '127.0.0.1' is restricted in accordance with IP Access restriction policy currently applied.

Cause

This is a Plesk bug with ID PPPM-12569, has already been fixed in Plesk Obsidian 18.0.32, which will become available the next week.

Resolution

As a temporary workaround, please use one of these solutions:

  • Use the URL with port 8443 when logging in to Plesk (https://example.com:8443).

  • Add the following code to the file /usr/local/psa/admin/conf/panel.ini:

    CONFIG_TEXT: [panel]
    realIpFrom = 127.0.0.1

    Note: Don't forget to remove the code once Plesk is updated to Obsidian 18.0.32.

Comments

5 comments

Sort by Date Votes
  • Avatar
    Beau Fiechter

    Bug does not seem te be fixed in 18.0.32 after removing this workaround. Still getting the error.

    2
    Comment actions Permalink
  • Avatar
    Ericbeck

    I have upgraded to 18.0.32 and the error is still there (as admin).  It is not there when using the https://<serverhostname>:8443 as the login, only when using the https://<serverhostname>/ to log in. 

    So ... to clarify:

    as customer: all good with or without :8443

    as admin: good with :8443, bad without  

    0
    Comment actions Permalink
  • Avatar
    Ericbeck

    Just to further clarify, the above comment is based on having the Custom URL set for logins.

    0
    Comment actions Permalink
  • Avatar
    Ericbeck

    So yesterday I did upgrade to 18.0.32 and this error was present as described above.  However, this morning, the error has disappeared, leading me to believe that some one of the daily cron jobs had to be run to remove this error and correct the bug with ID PPPM-12569. When Custom URL is in effect, and the admin tries to log in, AND the Plesk Firewall "IP Access Restriction Management" mode is set to disallow all IPs except for configured allowed IPs, the interface correctly reports access denied from the user's real IP address.  Yesterday, even after upgrading to 18.0.32 the reported error was there.

    Perhaps Plesk support could run a test starting with a server on 18.0.31, upgrade to 18.0.32 and before any daily crons have run, test the issue to confirm this behavior. Eric

    0
    Comment actions Permalink
  • Avatar
    Stewart

    I am on Plesk Obsidian for Windows  and have updated to 18.0.32 but still get the same error.

    Please can you confirm if this was indeed fixed in version 18.0.32

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles