• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Forwarded to devs Panel.ini setting doesn't work

Hex

Regular Pleskian
Plesk Certified Professional
TITLE:
Panel.ini setting doesn't work​
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
Plesk Obsidian 18.18
CentOS7-CL7
​
PROBLEM DESCRIPTION:
A custom redirect URL for the setting (gitub.redirectUrl) fallback to Confirm Sending Data instead of custom URL
so the github.redirectUrl is useless. :)

and google.redirectUrl the same​
STEPS TO REPRODUCE:
1-Download the github-sign-in.html and set a custom warining message.
2-Upload the file to a location e.i httpdocs
3-Go to panel.ini editor
4-Set custom URL
Code:
[ext-social-login]
github.redirectUrl = https://<domain>.<tld>/redirect/github-sign-in.html
5-login via github or edit profile to integrate.​
ACTUAL RESULT:
Falls back to the default URL​
EXPECTED RESULT:
Redirect to the custom URL​
ANY ADDITIONAL INFORMATION:
Also google shows 404 despite the correct app info in Google devs, I'm not sure until now if the issue is with my developers.google.com/console app or not, and there are no tutorial in Plesk docs explains how to create an App in Google with proper configurations.​
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Confirm bug​
 
Hi @Hextrator,
The ext-social-login options like redirectUrl, appId and appSecret are not intended to be used by Plesk administrators.
We did not declare support of custom login pages for Social login extension.

The reason why you found this is Panel.ini Editor extension is shown all available option even if they for internal usage only and do not supposed to be changed by customers. It also explains why we do not provide any guidelines.

Theoretically, you can use this functionality, but for this, you need to register your own application on the Github site, and properly set appId, appSecret and redirectUrl options.

And even in this case, we do not guarantee it will work:) So, it's not a bug, but current feature design.

Why do you want to change the default message? Do you have complains from end-customers regarding default wording?
 
It also explains why we do not provide any guidelines.
Yes, at least a note says : Not all settings are effective and it's a feature design or something.

Why do you want to change the default message? Do you have complains from end-customers regarding default wording?
Yes, Some customers have concerns about their data transferred somewhere else.

Anyway, Thank you for the clarification.
 
Back
Top