Websavers Inc
My feedback
19 results found
-
72 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.— rk
An error occurred while saving the comment An error occurred while saving the comment Websavers Inc
commented
Definitely need the ability to limit CPU and Memory for resellers...
Websavers Inc
supported this idea
·
-
1 vote
Thank you for your idea! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
-- PD
Websavers Inc
shared this idea
·
-
13 votes
Thank you for your input. We will consider this functionality in upcoming releases, if it will be popular.
Everyone, please continue voting for this feature if you consider it important.—
IGAn error occurred while saving the comment Websavers Inc
commented
Given that migrations are one of the most important methods of transferring away from CentOS 7 as it nears EOL, it sure would be handy if migrations could take care of migrating backup configurations as well, particularly for cloud connections.
Websavers Inc
supported this idea
·
-
25 votes
In the initital feature request it was not clear that the focus was on a regex driven, variable redirect that depends on source URLs and should be able to provide a mapping between source and target. It is also requested that these redirects shall be done on the front-end web server level, not as an Apache .htaccess solution.
We have re-opened the request as per user comment it was clarified thoroughly. We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
-- PD
An error occurred while saving the comment Websavers Inc
commented
This request is asking for variability of both source URL and destination URL and the ability to create more than one redirect.
What Plesk has provided thus far has been strictly the ability to create a single redirect with the source URL (and not subpaths of that URL) that redirect to a variable destination URL.
What is being requested here is the ability to create redirects that don't necessarily redirect the source website as a whole. Examples:
- sourcedomain.com/piglet/(.*) redirects to destinationdomain.com/pig/$1
- sourcedomain.com/donkey/(.*) redirects to destinationdomain.com/donkey/$1You cannot do this with Plesk without manually creating the nginx code or adding to the .htaccess file. Yet in cPanel you can as described in the screenshot provided by the OP.
Don't get me wrong, I greatly appreciate the functionality that has been provided so far.
However a totally separate 'advanced redirects' option would be very handy to have in the UI that generates nginx redirection configurations when nginx proxy is enabled and which generates apache mod_rewrite configurations when nginx proxy is not enabled.
This would avoid the need to utilize a redirections plugin in WordPress (or other CMS) which typically handles the redirections via PHP, which is far less efficient than doing it via the web server, and in particular via nginx.
An error occurred while saving the comment Websavers Inc
commented
The admin response here is not correct. You can add a domain alias and you can add a domain as a forward. However you cannot create custom redirects for any URL to any URL easily.
The only way to do this currently is via .htaccess which bypasses the performance of nginx.
It would be fantastic if there were a UI to add redirects that nginx handles without the need for an apache process.
Currently this can only be done by a Plesk admin via the apache & nginx settings page. It would be great if regular customers could manage their own redirects as well without it having to be done in .htaccess via apache.
An error occurred while saving the comment Websavers Inc
commented
Please link us to the documentation that shows we can create all forms of redirects in Plesk without using .htaccess or manually entering the syntax in the apache & nginx settings?
Websavers Inc
supported this idea
·
-
28 votes
Thank you for your input! We will consider this functionality for the upcoming releases if it becomes popular enough.
Everyone, please continue voting for this feature if you consider it important.
—
IGWebsavers Inc
supported this idea
·
-
7 votes
Thank you for your input. We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
—
IGWebsavers Inc
supported this idea
·
-
276 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
— IB
Websavers Inc
supported this idea
·
-
7 votes
Thank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IGWebsavers Inc
supported this idea
·
-
53 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
Websavers Inc
supported this idea
·
-
20 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
—
IGWebsavers Inc
supported this idea
·
-
2 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular. Everyone, please continue voting for this feature if you consider it important.
—
IGWebsavers Inc
supported this idea
·
-
629 votes
Repeatedly we're seeing questions on when http/3 will be implemented. http/3 is available in the experimental branch of Nginx, called "main line". This is not a branch that is "stable". Plesk only offers stable software versions for the utmost reliability you can get as reliability is much more important than speed. A fast website is of no use if its webserver crashes or the protocol doesn't work as expected in all cases. Plesk does not offer experimental features. The stable version of Nginx that supports http/3 is expected to become available in April 2024. This is when it makes sense for Plesk to also offer http/3.
From articles that foster the hype about http/3, it sounds as if it can increase a website's speed incredibly much. On average, on real website tests by several reknown sources, the acceleration has been seen at around 0.2 to 0.3 s/page, typically around 12…
Websavers Inc
supported this idea
·
-
14 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
— AY
Websavers Inc
supported this idea
·
-
17 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
—
IGWebsavers Inc
supported this idea
·
-
15 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
—
ETWebsavers Inc
supported this idea
·
-
442 votesWebsavers Inc
supported this idea
·
-
13 votesWebsavers Inc
supported this idea
·
-
4 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
—
ETWebsavers Inc
supported this idea
·
-
25 votesWebsavers Inc
supported this idea
·
Created a good workaround for this. It supports only CPU at the moment, but certainly welcome pull requests for memory and disk IO. https://github.com/websavers/Plesk-Event-Override-Cgroups-for-Resellers-Service-Plans/blob/main/plesk_reseller_serviceplan_event.sh