What Are You Doing Right Now
-
@nerdydad said in What Are You Doing Right Now:
Debian 9 with Ubiquiti's UCRM (ports 80 & 81) and UNMS (8080 & 8443) both installed by their install scripts.
Well that will do it.
-
@travisdh1 said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
@eddiejennings said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
Trying to install nginx but getting errors:
I have attempted installing with dependencies, but just not understanding this error. I'm being a total noob right now.
Apache wasn't installed at some point was it? That could be hogging port 80.
Not sure about apache. UCRM is installed at port 80.
@travisdh1 said in What Are You Doing Right Now:
@nerdydad What Distribution and version? Also, any custom repos? That just should not happen on a standard install of anything, uck.
Debian 9 with Ubiquiti's UCRM (ports 80 & 81) and UNMS (8080 & 8443) both installed by their install scripts.
Well... 2 services can't use the same port, and nginx will want to use port 80 by default. Look for the config file in /etc/nginx and comment out the port 80, and un-comment the port 443. You might have to do some more than just that......
Which begs the question, why do you want to run this on the same server? Having another server running an nginx proxy would be trivial resource wise.
Looking at purchasing a dedicated instance from Vultr and was considering combining both services to one server. Then Jared and Aaron mentioned Nginx and now I'm considering rebuilding this server again, but with nginx first, then the 2 services.
-
@nerdydad said in What Are You Doing Right Now:
@travisdh1 said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
@eddiejennings said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
Trying to install nginx but getting errors:
I have attempted installing with dependencies, but just not understanding this error. I'm being a total noob right now.
Apache wasn't installed at some point was it? That could be hogging port 80.
Not sure about apache. UCRM is installed at port 80.
@travisdh1 said in What Are You Doing Right Now:
@nerdydad What Distribution and version? Also, any custom repos? That just should not happen on a standard install of anything, uck.
Debian 9 with Ubiquiti's UCRM (ports 80 & 81) and UNMS (8080 & 8443) both installed by their install scripts.
Well... 2 services can't use the same port, and nginx will want to use port 80 by default. Look for the config file in /etc/nginx and comment out the port 80, and un-comment the port 443. You might have to do some more than just that......
Which begs the question, why do you want to run this on the same server? Having another server running an nginx proxy would be trivial resource wise.
Looking at purchasing a dedicated instance from Vultr and was considering combining both services to one server. Then Jared and Aaron mentioned Nginx and now I'm considering rebuilding this server again, but with nginx first, then the 2 services.
That won't really help. In both cases, you have to change the ports of the other services.
-
@scottalanmiller said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
@travisdh1 said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
@eddiejennings said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
Trying to install nginx but getting errors:
I have attempted installing with dependencies, but just not understanding this error. I'm being a total noob right now.
Apache wasn't installed at some point was it? That could be hogging port 80.
Not sure about apache. UCRM is installed at port 80.
@travisdh1 said in What Are You Doing Right Now:
@nerdydad What Distribution and version? Also, any custom repos? That just should not happen on a standard install of anything, uck.
Debian 9 with Ubiquiti's UCRM (ports 80 & 81) and UNMS (8080 & 8443) both installed by their install scripts.
Well... 2 services can't use the same port, and nginx will want to use port 80 by default. Look for the config file in /etc/nginx and comment out the port 80, and un-comment the port 443. You might have to do some more than just that......
Which begs the question, why do you want to run this on the same server? Having another server running an nginx proxy would be trivial resource wise.
Looking at purchasing a dedicated instance from Vultr and was considering combining both services to one server. Then Jared and Aaron mentioned Nginx and now I'm considering rebuilding this server again, but with nginx first, then the 2 services.
That won't really help. In both cases, you have to change the ports of the other services.
That's fine about ports as long as it can forward from a sub-domain. But this leads me to 2 questions:
- How will this affect communications with my equipment when deployed and into production?
- What features does this add to the server? Better security?
Definitely adds a layer of complexity to the mix.
-
@nerdydad said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
@travisdh1 said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
@eddiejennings said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
Trying to install nginx but getting errors:
I have attempted installing with dependencies, but just not understanding this error. I'm being a total noob right now.
Apache wasn't installed at some point was it? That could be hogging port 80.
Not sure about apache. UCRM is installed at port 80.
@travisdh1 said in What Are You Doing Right Now:
@nerdydad What Distribution and version? Also, any custom repos? That just should not happen on a standard install of anything, uck.
Debian 9 with Ubiquiti's UCRM (ports 80 & 81) and UNMS (8080 & 8443) both installed by their install scripts.
Well... 2 services can't use the same port, and nginx will want to use port 80 by default. Look for the config file in /etc/nginx and comment out the port 80, and un-comment the port 443. You might have to do some more than just that......
Which begs the question, why do you want to run this on the same server? Having another server running an nginx proxy would be trivial resource wise.
Looking at purchasing a dedicated instance from Vultr and was considering combining both services to one server. Then Jared and Aaron mentioned Nginx and now I'm considering rebuilding this server again, but with nginx first, then the 2 services.
That won't really help. In both cases, you have to change the ports of the other services.
That's fine about ports as long as it can forward from a sub-domain. But this leads me to 2 questions:
- How will this affect communications with my equipment when deployed and into production?
- What features does this add to the server? Better security?
Definitely adds a layer of complexity to the mix.
But eliminate a complete server.
-
@RojoLoco found out that we are talking about opening an Atlanta office.
-
@scottalanmiller said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
@travisdh1 said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
@eddiejennings said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
Trying to install nginx but getting errors:
I have attempted installing with dependencies, but just not understanding this error. I'm being a total noob right now.
Apache wasn't installed at some point was it? That could be hogging port 80.
Not sure about apache. UCRM is installed at port 80.
@travisdh1 said in What Are You Doing Right Now:
@nerdydad What Distribution and version? Also, any custom repos? That just should not happen on a standard install of anything, uck.
Debian 9 with Ubiquiti's UCRM (ports 80 & 81) and UNMS (8080 & 8443) both installed by their install scripts.
Well... 2 services can't use the same port, and nginx will want to use port 80 by default. Look for the config file in /etc/nginx and comment out the port 80, and un-comment the port 443. You might have to do some more than just that......
Which begs the question, why do you want to run this on the same server? Having another server running an nginx proxy would be trivial resource wise.
Looking at purchasing a dedicated instance from Vultr and was considering combining both services to one server. Then Jared and Aaron mentioned Nginx and now I'm considering rebuilding this server again, but with nginx first, then the 2 services.
That won't really help. In both cases, you have to change the ports of the other services.
That's fine about ports as long as it can forward from a sub-domain. But this leads me to 2 questions:
- How will this affect communications with my equipment when deployed and into production?
- What features does this add to the server? Better security?
Definitely adds a layer of complexity to the mix.
But eliminate a complete server.
Sorry, I'm not following. Is nginx supposed to be its own server or separate the 2 services?
-
@brianlittlejohn said in What Are You Doing Right Now:
Anybody looking, Vultr has storage instances available in their LA datacenter
can you convert a VM on Vultr from one type to another?
-
@nerdydad said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
@travisdh1 said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
@eddiejennings said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
Trying to install nginx but getting errors:
I have attempted installing with dependencies, but just not understanding this error. I'm being a total noob right now.
Apache wasn't installed at some point was it? That could be hogging port 80.
Not sure about apache. UCRM is installed at port 80.
@travisdh1 said in What Are You Doing Right Now:
@nerdydad What Distribution and version? Also, any custom repos? That just should not happen on a standard install of anything, uck.
Debian 9 with Ubiquiti's UCRM (ports 80 & 81) and UNMS (8080 & 8443) both installed by their install scripts.
Well... 2 services can't use the same port, and nginx will want to use port 80 by default. Look for the config file in /etc/nginx and comment out the port 80, and un-comment the port 443. You might have to do some more than just that......
Which begs the question, why do you want to run this on the same server? Having another server running an nginx proxy would be trivial resource wise.
Looking at purchasing a dedicated instance from Vultr and was considering combining both services to one server. Then Jared and Aaron mentioned Nginx and now I'm considering rebuilding this server again, but with nginx first, then the 2 services.
That won't really help. In both cases, you have to change the ports of the other services.
That's fine about ports as long as it can forward from a sub-domain. But this leads me to 2 questions:
- How will this affect communications with my equipment when deployed and into production?
- What features does this add to the server? Better security?
Definitely adds a layer of complexity to the mix.
But eliminate a complete server.
Sorry, I'm not following. Is nginx supposed to be its own server or separate the 2 services?
Nginx is just a web server. You generally use it as a proxy in front of other services so that you have caching and control.
-
@dashrender said in What Are You Doing Right Now:
@brianlittlejohn said in What Are You Doing Right Now:
Anybody looking, Vultr has storage instances available in their LA datacenter
can you convert a VM on Vultr from one type to another?
No
-
@scottalanmiller said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
@travisdh1 said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
@eddiejennings said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
Trying to install nginx but getting errors:
I have attempted installing with dependencies, but just not understanding this error. I'm being a total noob right now.
Apache wasn't installed at some point was it? That could be hogging port 80.
Not sure about apache. UCRM is installed at port 80.
@travisdh1 said in What Are You Doing Right Now:
@nerdydad What Distribution and version? Also, any custom repos? That just should not happen on a standard install of anything, uck.
Debian 9 with Ubiquiti's UCRM (ports 80 & 81) and UNMS (8080 & 8443) both installed by their install scripts.
Well... 2 services can't use the same port, and nginx will want to use port 80 by default. Look for the config file in /etc/nginx and comment out the port 80, and un-comment the port 443. You might have to do some more than just that......
Which begs the question, why do you want to run this on the same server? Having another server running an nginx proxy would be trivial resource wise.
Looking at purchasing a dedicated instance from Vultr and was considering combining both services to one server. Then Jared and Aaron mentioned Nginx and now I'm considering rebuilding this server again, but with nginx first, then the 2 services.
That won't really help. In both cases, you have to change the ports of the other services.
That's fine about ports as long as it can forward from a sub-domain. But this leads me to 2 questions:
- How will this affect communications with my equipment when deployed and into production?
- What features does this add to the server? Better security?
Definitely adds a layer of complexity to the mix.
But eliminate a complete server.
Sorry, I'm not following. Is nginx supposed to be its own server or separate the 2 services?
Nginx is just a web server. You generally use it as a proxy in front of other services so that you have caching and control.
Any other recommendations for preparing (hardening) the server to face the public?
-
@nerdydad said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
@travisdh1 said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
@eddiejennings said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
Trying to install nginx but getting errors:
I have attempted installing with dependencies, but just not understanding this error. I'm being a total noob right now.
Apache wasn't installed at some point was it? That could be hogging port 80.
Not sure about apache. UCRM is installed at port 80.
@travisdh1 said in What Are You Doing Right Now:
@nerdydad What Distribution and version? Also, any custom repos? That just should not happen on a standard install of anything, uck.
Debian 9 with Ubiquiti's UCRM (ports 80 & 81) and UNMS (8080 & 8443) both installed by their install scripts.
Well... 2 services can't use the same port, and nginx will want to use port 80 by default. Look for the config file in /etc/nginx and comment out the port 80, and un-comment the port 443. You might have to do some more than just that......
Which begs the question, why do you want to run this on the same server? Having another server running an nginx proxy would be trivial resource wise.
Looking at purchasing a dedicated instance from Vultr and was considering combining both services to one server. Then Jared and Aaron mentioned Nginx and now I'm considering rebuilding this server again, but with nginx first, then the 2 services.
That won't really help. In both cases, you have to change the ports of the other services.
That's fine about ports as long as it can forward from a sub-domain. But this leads me to 2 questions:
- How will this affect communications with my equipment when deployed and into production?
- What features does this add to the server? Better security?
Definitely adds a layer of complexity to the mix.
But eliminate a complete server.
Sorry, I'm not following. Is nginx supposed to be its own server or separate the 2 services?
Nginx is just a web server. You generally use it as a proxy in front of other services so that you have caching and control.
Any other recommendations for preparing (hardening) the server to face the public?
Make sure there's a network firewall before the server, only allowing the ports through that you are using on the server.
Make sure SELinux is on, and linux firewall is configured well.
-
@scottalanmiller said in What Are You Doing Right Now:
@dashrender said in What Are You Doing Right Now:
@brianlittlejohn said in What Are You Doing Right Now:
Anybody looking, Vultr has storage instances available in their LA datacenter
can you convert a VM on Vultr from one type to another?
No
yeah, was afraid of that.. and this new instance would be in a different DC than my current one.. no telling how fast 80 GB data would move.. though I'm beting pretty good.
-
@nerdydad said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
@travisdh1 said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
@eddiejennings said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
Trying to install nginx but getting errors:
I have attempted installing with dependencies, but just not understanding this error. I'm being a total noob right now.
Apache wasn't installed at some point was it? That could be hogging port 80.
Not sure about apache. UCRM is installed at port 80.
@travisdh1 said in What Are You Doing Right Now:
@nerdydad What Distribution and version? Also, any custom repos? That just should not happen on a standard install of anything, uck.
Debian 9 with Ubiquiti's UCRM (ports 80 & 81) and UNMS (8080 & 8443) both installed by their install scripts.
Well... 2 services can't use the same port, and nginx will want to use port 80 by default. Look for the config file in /etc/nginx and comment out the port 80, and un-comment the port 443. You might have to do some more than just that......
Which begs the question, why do you want to run this on the same server? Having another server running an nginx proxy would be trivial resource wise.
Looking at purchasing a dedicated instance from Vultr and was considering combining both services to one server. Then Jared and Aaron mentioned Nginx and now I'm considering rebuilding this server again, but with nginx first, then the 2 services.
That won't really help. In both cases, you have to change the ports of the other services.
That's fine about ports as long as it can forward from a sub-domain. But this leads me to 2 questions:
- How will this affect communications with my equipment when deployed and into production?
- What features does this add to the server? Better security?
Definitely adds a layer of complexity to the mix.
But eliminate a complete server.
Sorry, I'm not following. Is nginx supposed to be its own server or separate the 2 services?
Nginx is just a web server. You generally use it as a proxy in front of other services so that you have caching and control.
Any other recommendations for preparing (hardening) the server to face the public?
Turn on automatic security updates.
-
@nerdydad said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
@travisdh1 said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
@eddiejennings said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
Trying to install nginx but getting errors:
I have attempted installing with dependencies, but just not understanding this error. I'm being a total noob right now.
Apache wasn't installed at some point was it? That could be hogging port 80.
Not sure about apache. UCRM is installed at port 80.
@travisdh1 said in What Are You Doing Right Now:
@nerdydad What Distribution and version? Also, any custom repos? That just should not happen on a standard install of anything, uck.
Debian 9 with Ubiquiti's UCRM (ports 80 & 81) and UNMS (8080 & 8443) both installed by their install scripts.
Well... 2 services can't use the same port, and nginx will want to use port 80 by default. Look for the config file in /etc/nginx and comment out the port 80, and un-comment the port 443. You might have to do some more than just that......
Which begs the question, why do you want to run this on the same server? Having another server running an nginx proxy would be trivial resource wise.
Looking at purchasing a dedicated instance from Vultr and was considering combining both services to one server. Then Jared and Aaron mentioned Nginx and now I'm considering rebuilding this server again, but with nginx first, then the 2 services.
That won't really help. In both cases, you have to change the ports of the other services.
That's fine about ports as long as it can forward from a sub-domain. But this leads me to 2 questions:
- How will this affect communications with my equipment when deployed and into production?
- What features does this add to the server? Better security?
Definitely adds a layer of complexity to the mix.
But eliminate a complete server.
Sorry, I'm not following. Is nginx supposed to be its own server or separate the 2 services?
Nginx is just a web server. You generally use it as a proxy in front of other services so that you have caching and control.
Any other recommendations for preparing (hardening) the server to face the public?
Hopefully Vultr keeps their servers firmware up to date.
-
@dashrender said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@dashrender said in What Are You Doing Right Now:
@brianlittlejohn said in What Are You Doing Right Now:
Anybody looking, Vultr has storage instances available in their LA datacenter
can you convert a VM on Vultr from one type to another?
No
yeah, was afraid of that.. and this new instance would be in a different DC than my current one.. no telling how fast 80 GB data would move.. though I'm beting pretty good.
Yeah, that is pretty small.
-
I've built seventeen servers on Vultr TODAY. lol
-
Rolling out another Fedora 26 desktop in the office. First of the Windows people considering converting.
-
@scottalanmiller said in What Are You Doing Right Now:
I've built seventeen servers on Vultr TODAY. lol
That's a lot.
All for a single customer?
-
@nerdydad said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
@travisdh1 said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
@eddiejennings said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
Trying to install nginx but getting errors:
I have attempted installing with dependencies, but just not understanding this error. I'm being a total noob right now.
Apache wasn't installed at some point was it? That could be hogging port 80.
Not sure about apache. UCRM is installed at port 80.
@travisdh1 said in What Are You Doing Right Now:
@nerdydad What Distribution and version? Also, any custom repos? That just should not happen on a standard install of anything, uck.
Debian 9 with Ubiquiti's UCRM (ports 80 & 81) and UNMS (8080 & 8443) both installed by their install scripts.
Well... 2 services can't use the same port, and nginx will want to use port 80 by default. Look for the config file in /etc/nginx and comment out the port 80, and un-comment the port 443. You might have to do some more than just that......
Which begs the question, why do you want to run this on the same server? Having another server running an nginx proxy would be trivial resource wise.
Looking at purchasing a dedicated instance from Vultr and was considering combining both services to one server. Then Jared and Aaron mentioned Nginx and now I'm considering rebuilding this server again, but with nginx first, then the 2 services.
That won't really help. In both cases, you have to change the ports of the other services.
That's fine about ports as long as it can forward from a sub-domain. But this leads me to 2 questions:
- How will this affect communications with my equipment when deployed and into production?
- What features does this add to the server? Better security?
Definitely adds a layer of complexity to the mix.
But eliminate a complete server.
Sorry, I'm not following. Is nginx supposed to be its own server or separate the 2 services?
Nginx is just a web server. You generally use it as a proxy in front of other services so that you have caching and control.
Any other recommendations for preparing (hardening) the server to face the public?
Keep it turned off and unplugged? The public is rough!
