Bug when adding website

wav3front

Hi!

I have selected these two options in the package that the customer uses:

Customer stickiness
Subscription stickiness

The customer's websites are already on my node1 production server.
However, when they add a new website, it's actually placed on my control panel (Enhance) server which is not supposed to be used for customers at all.

This brings two concerns:

The above options do not work?
We should be able to mark the CP server as not available for customers.

gmakhs

wav3front you can disable provisioning on the control panel server from server settings , customer stickiness options are buggy and even if new websites are on the same server , staging websites are not following the stickiness I reported such issues on v11 I hope they fix it on V12 though I don't see something on the roadmap

cPFence

wav3front This brings two concerns:
The above options do not work?
We should be able to mark the CP server as not available for customers.

1 – We tried the “Customer stickiness” option before and found it a bit complicated, and it didn’t seem to work as expected. Just go with the method shared by @rdbf , it's simple and works well.

2 – To prevent customer sites from being placed on the CP server: go to Servers > Main CP > Application > Disable Placement.

rdbf

Create server groups (even groups of 1 will do), and define the group to be used in the package. Customers on that package will always be placed on the server(s) in that group then.

wav3front

gmakhs that’s very unfortunate.

@Aliysa_Enhance could we please have an update on this bug?🐞

Aliysa_Enhance

wav3front for disabling placement on your cp server see https://enhance.com/docs/server-management/website-server-placement.html#disable-website-placement-on-a-server

Regarding the issue you are facing, can you please send a ticket in and we’ll look into it for you.