• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question Does someone set Ubnt Unify Controller on the same server with Plesk?

kojot

Regular Pleskian
I found only one google result, with using docker.
Does someone set that also?
Please provide short instructions how you managed it.
 
It's been a while but I believe it utilized Port 8443 as well so you'd have to change the port the controller listens on.... i'd be leery though as you'll never know if it would cause conflicts with Plesk in the long run. I've been out of that scene for too long, but a lot of people were using AWS or Rackspace or the like to run their controllers.
 
Yes, my first thought was that port 8443 will be a problem, because that I started this thread, just to see other experiences.
And yes AWS can be solution, but for now I need it for only two AP, so it would be better if I can use it somehow with some of our existing servers. But on our servers we have already Plesk installed.
 
Seems like some folks are already using a pre built docker container;

Ubiquiti Networks Community

This would be the safe route. You’d be able to map port 8443 on the docker container to an alternative port on the public IP.

I say you’d probably be like 99% safe installing it directly on the server once you change up the port though.
 
Back
Top