• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

multiple users on the same IP

Jllynch

Regular Pleskian
Is there a chance that multiple users sitting behind the same public IP address on different computers (via a router) may cause conflicts in their site if they are both editing different sites at the same time? Could there be a clash/corruption?
 
Justin, in this case everything should work correctly also. Users will be logged into their own area and have access only to their data without any conflicts.
There can be possible conflict in using feedback module on both sites, for example. If there is a limit setup for using feedback it will not allow send two feedbacks one by one within 30 minutes from one IP address. This is default restrictions and can be redefined in /SB_ROOT/config file:

[feedback]

limit_for_next_send_message = TIME (in minutes)

Hope this answers the question.
 
Back
Top