Facebook
TwitterOh yes, it's probably because my provider has not updated repository:
Index of /
Index of /
-
We value your experience with Plesk during 2024
Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
Please take this short survey:
https://pt-research.typeform.com/to/AmZvSXkx -
The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
-
We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.
Plesk 17.8 RTM has been released
- Thread starter korsar
- Start date
-
- Tags
- release notes
- Status
MitchellvB995
Basic Pleskian
I still wouldn’t recommend updating because there are still many bugs not solved.
What actual bugs have you encountered?
MitchellvB995
Basic Pleskian
Well, maybe there are not ‘many’ bugs, but still an important one, at least on my Debian 8 Server: Disk usage is ‘still’ not being displayed correctly.
Hi @MitchellvB995,
Please expect the fix of this issue in the next micro-update #3. The issue id is PPP-35732.
Please tell me, how many times have you asked this question?
Kingsley
Silver Pleskian
because i have not been giving an answer for the early adopter release
Yes. You could also use Windows 95.... now is it right for you? That's your decision.
Kingsley
Silver Pleskian
why would i use windows 95?
Why not? It's probably the most stable version of Windows out there.
Kingsley
Silver Pleskian
where did you see me ask which OS to use? you are trying to make fun of the situation
Alejandro Oro Vojacek
Basic Pleskian
I just upgraded. My server nginx config is now broken. I would say DON'T.
No any details?
Alejandro Oro Vojacek
Basic Pleskian
Everything is working now. I have to give it to Plesk they were very helpful in helping me solve the issues.
Hajime Tanaka
Regular Pleskian
Just updated to Plesk Oynx 17.8.11, before from 17.5.3.
Plesk Onyx logged successfully then still keep going to receive me to "Subscribe to our newsletters"
I entered "Consent and Subscribe" & "No, Thanks.", then they said: Could not save your subscription status.
Hajime Tanaka
Regular Pleskian
Never mind, It's oddly so. I blocked banner for this alert up from AdGurad. Refresh then "My profile > Newsletters > enable" It works fine.
learning_curve
Golden Pleskian
We're not involved in any of the Early Adopter / General Release for 17.8.11 confusion above, because it's been explained very clearly (we think). Our Plesk setup is General Release and Safe Updates For System Packages only, so is quite smooth running (but we do customise things ourselves sometimes too). Our experience is very good so far, with both Plesk itself and this forum.
Looking forward, we'd like to upgrade to a General Release 17.8.11 installation that runs everything (and we mean everything) at TLSv1.3
Yes TLSv1.3 is still not officially released yet, so yes this means there's plenty of patience required from everyone. However, looking forward again just from a Plesk perspective: This WILL need a recompiled / respecified / re-worked sw-cp-server to accompany a General Release 17.8.11 Plesk Installation. We've answered a question about this already, but we haven't got an answer from anybody at Plesk... yet. It's a fairly basic system requirement, especially as the current sw-cp-server is massively out of date Can anybody from Plesk and/or forum members advise a future roadmap inclusion / plan / ETA / a.n.other future self compiling option for this, if, it's still not planned to be provided by Plesk as part of 17.8.11? It feels like it's shrowded in mystery, yet it is such a simple job (by comparison) in relation to all the related 17.5.3. > 17.8.11 upgrade work.
All the other items we think are needed after the Plesk 17.5.3. > 17.8.11 upgrade e.g. openssl upgrade / openssl within php upgrade plus many other custom changes outside of Plesk and/or Distro should all be able to be achieved relatively easily thanks mainly to good reference info within this forum but occasionally from outside it too sw-cp-server.... your time is up
Looking forward, we'd like to upgrade to a General Release 17.8.11 installation that runs everything (and we mean everything) at TLSv1.3
Yes TLSv1.3 is still not officially released yet, so yes this means there's plenty of patience required from everyone. However, looking forward again just from a Plesk perspective: This WILL need a recompiled / respecified / re-worked sw-cp-server to accompany a General Release 17.8.11 Plesk Installation. We've answered a question about this already, but we haven't got an answer from anybody at Plesk... yet. It's a fairly basic system requirement, especially as the current sw-cp-server is massively out of date Can anybody from Plesk and/or forum members advise a future roadmap inclusion / plan / ETA / a.n.other future self compiling option for this, if, it's still not planned to be provided by Plesk as part of 17.8.11? It feels like it's shrowded in mystery, yet it is such a simple job (by comparison) in relation to all the related 17.5.3. > 17.8.11 upgrade work.All the other items we think are needed after the Plesk 17.5.3. > 17.8.11 upgrade e.g. openssl upgrade / openssl within php upgrade plus many other custom changes outside of Plesk and/or Distro should all be able to be achieved relatively
easily thanks mainly to good reference info within this forum but occasionally from outside it too sw-cp-server.... your time is up - Status
Similar threads
