Question checking for outdated/obsolete panel.ini options

[TomBoB]

Server operating system version

Almalinux 8

Plesk version and microupdate number

18.0.49 #2

Hi,

Plesk throws additional options into the panel.ini ring every so often. But barely ever says anything about the ones becoming obsolete or no longer necessary (as it became default for example).

Please glance over if you spot any obsolete ones. - It's our basic active one for most servers; maybe some people might also find it useful for ideas.

[login]
howToLoginArticle = ''
[gdpr]
cookieSettings.loginFormEntrypointEnabled = false
[facebook]
showLikeLink = true
pleskPage = https://www.facebook.com/ourcompany/
[twitter]
showFollowLink = false
[rating]
enabled = false
[product]
siteUrl = https://ourcompany.com/website-hosting/
[promos]
enabled = false
pleskFooter = false
[aps]
serverAppsPromoEnabled = false
[api]
deprecationWarning = off
; to restrict access to the API. In Order: ISP1,ISP2  HAS BUG !! DON'T DO !!
; allowedIPs = 1.2.3.4,2.3.4.5
[techDomain]
subdomain.enabled = false
; disable feature of creating a temp domain name provided by Plesk
[dns]
enableResolveChecking = false
; disables resolve checking
; showDndHelper = false ; hides DNS helper
[feedback]
userVoice = false
sentry.dsn = ""
[userActivityTracking]
enabled = false
[navigation]
collapseSecondarySidebar = false
hideWebsiteList = classic
[domainManagement]
applicationWizard.enabled = false
settings.autoSelectIpv6 = on
[ext-sslit]
enableSecuringNewDomain = true
; shows the section to secure during subscription creation
secure-new-domain = true
; ticks the box to secure with lets encrypt
showGetMoreCertificatesLink = false
[ext-letsencrypt]
require-www-webmail-sans = true
; don’t disable www and webmail from getting cert when first attempt failed
rsa-key-size = 4096
acme-directory-url = "https://acme-v02.api.letsencrypt.org/directory"
acme-protocol-version = "acme-v02"
key-algorithm = RSA
[ext-wp-toolkit]
showSmartUpdates = false
[ext-catalog]
contextAds = false
extensionUpload = true
[ext-advisor]
blacklist = KernelCare,ImunifyQuickPatch,SpeedKit,PageSpeed,SeoToolkit,Acronis,CloudPro,Imunify360,SectigoSsl,Platform360_PleskSynergy
[websitesDiagnostic]
enabled = true
[webserver]
xPoweredByHeader = off
restartApacheWhenChangingFpmHandler = 1
; if apache restart is non-zero, this forces restart anyway
[notification]
; user the PROPER SERVER DOMAINs email for this
senderAddress=postmaster@ourcompany.com
[mail]
clientConfig.incomingProtocols = "POP3 over SSL/TLS port 995, IMAP over SSL/TLS port 993"
clientConfig.outgoingProtocols = "SMTP over STARTTLS/Auto, port 587"
clientConfig.hideSslNote = true
clientConfig.smtpPortEncrypted = 587

Thanks for any input.

 

[Kaspar]

It certainly would be nice if there was documentation available on deprecated panel.ini settings.

I could not spot any settings on you list that seemed out of the ordinary to me. But it I am not 100% which settings are deprecated. I am however intrigued by the comment in your list that states:

to restrict access to the API. In Order: ISP1,ISP2 HAS BUG !! DON'T DO !!

What bug are you referring too?

 

[TomBoB]

Maybe a year or two ago we tested out that setting as we wanted to limit access via the API. Turned out that feature didn't work as it had a bug. Pretty sure we filed a bug report for that. But as we went in a different direction we didn't need that setting anymore and by the looks we simply left/forgot that comment in there.

EDIT: This one. Forwarded to devs - access limitation to API - Plesk Mobile Extension doesn't handle it correctly

 

[Peter Debik]

The issue [PMBL-615] has not been resolved yet. It has some impact, but it also seems that the underlying feature is very rarely used so that other issues still have higher priority for resolution.

 

[TomBoB]

Thanks for the update, Peter.