Memescape
My feedback
9 results found
-
386 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
An error occurred while saving the comment Memescape supported this idea ·
-
368 votes
Thank you for your input. We will consider the possibility of implementing this feature in upcoming releases.
— ES
Memescape supported this idea ·
-
544 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.
—
IGMemescape supported this idea ·
-
436 votes
Memescape supported this idea ·
-
569 votes
Since Plesk Onyx you will be able to install memcache as a Docker container and configure http(s) proxy rule for it to map to your web app.
Docker and proxy rules are available in Plesk Onyx Preview already, you can try it here https://talk.plesk.com/threads/plesk-onyx-preview-and-feedback.337172/
SE
Memescape supported this idea ·
-
713 votes
As an alternative option, you can configure GeoIP protection using nginx GeoIP module https://docs.plesk.com/en-US/obsidian/administrator-guide/website-management/websites-and-domains/extended-website-management/plesk-for-linux-setting-up-ip-geolocation-for-a-website.80011/
Please let us know what you think about it.
--AA
Memescape supported this idea ·
-
676 votes
Memescape supported this idea ·
-
1,177 votes
Memescape supported this idea ·
-
10 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.
—
IGMemescape supported this idea ·
Definitely a +1 for this.
Being able to relay to an external SMTP is needed for users who provide hosting services on platforms like Digital Ocean. DO only support one rDNS record so in a shared hosting environment where many domains share a single IP, some mail providers flag email send from the domains as spam because the domain name lookup does not match the reverse lookup for the IP. As such, it's essential to be able to route through a 3rd-party (like Amazon SES, SendGrid, Mailgun, etc.).