Install Gluu on server with Plesk, both in Root?

By: Justin Chen user 19 May 2018 at 4:14 p.m. CDT

4 Responses
Justin Chen gravatar
**The Question:** Is it wrong to run Plesk and Gluu on the same _dedicated, unpartitioned_ server (aka, they are both installed in root). **The Details:** Hey guys, have a conundrum here. I have a dedicated server with 16.04 on it and Plesk. I configured the server for Gluu, and found I couldn't get Gluu to install without changing some Nginx ports (their default was 80 and 443, which I changed to 81 and 444). Then I discovered that the Apache2 that came with Plesk was using the 80 and 443. It appears that on install, Gluu wants to install its own Apache2 and wouldn't let me install because of the apache already installed. I got around this by stopping the Apache2 service through Plesk then going ahead with the installation. I tried to restart Apache2 through plesk, and it killed the Gluu server. To restart it: 1. I had to stop the apache2 through Plesk services 2. I then had to restart gluu service, and it didn't load the login page 3. I then opened chroot / in SSH and restarted apache through there 4. Gluu was then working again So I guess I found that I have two Apache instances that can conflict. And when the "Plesk Apache" is off, I can't load any webpages. So I have to choose between Gluu or loading webpages. Which is totally fine as the server, unless I create some virtual machines, probably shouldn't load webpages from the same place as Gluu. **So I guess I'm wondering:** 1. Since I can't use the server for websites at the same time as Gluu, should I wipe the server with a basic linux and reinstall Gluu without Plesk? 2. If no, are there any inherent problems with leaving Plesk on? Thanks in advanced!
Ubuntu 16.04
closed

Answers

By Michael Schwartz Account Admin 19 May 2018 at 4:18 p.m. CDT

Copy
Michael Schwartz gravatar
Of course you need to worry about port conflicts. If you don't want to change the ports, you can configure a virtual ethernet adapter (i.e. eth0:0), assign it a differnt ip, and make sure when you run setup, you use the virtual adapter. A quick google search turned up this article: [Configuring virtual network interfaces in Linux](https://linuxconfig.org/configuring-virtual-network-interfaces-in-linux)

By Justin Chen user 19 May 2018 at 10:30 p.m. CDT

Copy
Justin Chen gravatar
I guess I wasn't super clear. I had the port thing figured out. I'm just wondering if there is anything intrinsically wrong with running Gluu on the same server as Plesk setup on it. As long as I keep Plesk's Apache2 off, there is no port conflict. I fixed that already.

By Michael Schwartz Account Admin 20 May 2018 at 1:26 a.m. CDT

Copy
Michael Schwartz gravatar
It's contrary to current trends in isolation of services. Any vulnerability in Plesk could lead to compromise of your private keys for your federation services. So for a test server it's ok. But in prod it's a really bad idea.

By Justin Chen user 20 May 2018 at 1:33 a.m. CDT

Copy
Justin Chen gravatar
That's kinda what I figured... Appreciate the frank reply. I'll re-image the server with a minimal Ubuntu 16.04 install and go from there.

Post an answer