Updating cloned backend in WebGUI updates the original backend instead of the cloned backend
This bug has appeared for me 3 times now when I clone an existing https to a new backend.
I have multiple SSL sites on the same IP so for me it is simplest to clone an existing frontend/backend to keep the custom settings.
- I clone a backend.
- Edit the new cloned backend, change the ipaddress/hostname to the correct one.
- When I check the old backend which was used for cloning it now has the ip/hostname of the cloned backend.
- Not completely sure but I believe the cloned backend was changed as well to the correct ip/hostname
haproxy 0.48 / pfsense 2.3.2
This will probably happen again so I will take more notes when it does.
#1 Updated by Pi Ba over 3 years ago
I think it fixed in 0.50 .
In the mean time save the backend directly after cloning, then reopen it to make wanted changes.