I know! That’s why I told you to enable it.
Apache is also not dependent on Virtualmin. When I tell you that you can do anything you want manually, I mean it. Which is why I’m so baffled you believe Virtualmin is restricting you in some way.
Failed to save enabled features : The Apache configuration on your system does not appear to be listening on port 443, which is needed to host SSL websites. If you do not plan to host SSL sites, this feature should be disabled in Virtualmin’s module configuration page
It’s fine that Apache isn’t listening on port 80, but it’s not fine that it’s not listening on 443? See what I mean by arbitrary confusing restrictions?
Wait. What’s listening on 443?
Maybe I am recommending you reinstall. If you want nginx to be your web server, you should use the LEMP install.
1 Like
Nginx was listening on 443. I stopped it, restarted Apache listening on 443 and that did it.
Would reinstalling with LEMP improve Nginx support in Virtualmin? Hopefully without breaking Apache?
No.
The two are mutually exclusive. As I said, there is no support for both at the same time in Virtualmin (and will not be).
Pick the one you want to be managed by Virtualmin, and use that install type. If you also want the other one hanging around for some reason, then install it yourself and configure it manually in whatever way you choose (or automate it with post-change scripts in Virtualmin or whatever). We won’t be implementing that kind of support and there is no support for both at the same time. But, again, Virtualmin absolutely 100% does not stop you from doing it…but it’s not going to help.
Edit: To be clear, “does not support” continues to not mean “prohibits”. But, you are not going to have GUI support written by us for managing both nginx and Apache at the same time on the same system. We will support your use of nginx, or we will support your use of Apache. Anything else, go with our best wishes, but that’s all you’re getting out of us.
1 Like
Yeah I meant to ask which one is better supported by Virtualmin, because Stefan said Apache is better supported. You’re right though, my choice should come down to convenience. Since I’m less experienced with Nginx, I could use the GUI support for it as opposed to Apache that I can set up entirely on my own.
Thank you for your help and patience. And once again I apologize for any perceived rudeness. In hindsight the binary choice at installation should have made it obvious that I can’t have both.
Apache has a lot more users and a lot more testing and has been in Virtualmin (and Webmin) longer. So, it is better supported. But, nginx is pretty much full-featured at this point, too.
I said I use it, I don’t recall saying its better. I’ve never used Nginx. Alot of other users use it and prob says its better but its a foreign setup for me.
@crossroads Hi, it sounds to me that you want both Apache and Nginx on the same VM → just ignore this if I am wrong.
You know about Apache as a webserver and would like to use (even experiment with) Nginx webserver.
I used to use Apache and have since come to detest it and now use Nginx exclusively. As has already been said Virtualmin does not support both together. I was also confused for a while as a relative new comer to Virtualmin because so much seemed to revolve around or assume Apache (well understandable) but even when one goes down the LEMP install route there remain references to Apache that are redundant.
What I did initially was to create 2 totally separate VMs (one LAMP and one LEMP) that helped with quite a lot of the learning. I have since destroyed the LAMP VM starting clean again with another LEMP. (and now dislike Apache even more) But I find that Virtualmin does a very good job. (OK I still get the occasional issue and cry for help - but usually find it is my, often silly, misunderstanding)
I think separate VMs would solve your problem. Either way just persevere.
This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.