ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    What Are You Doing Right Now

    Water Closet
    time waster
    285
    88.9k
    41.9m
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • travisdh1T
      travisdh1 @NerdyDad
      last edited by

      @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.

      NerdyDadN 1 Reply Last reply Reply Quote 0
      • scottalanmillerS
        scottalanmiller @NerdyDad
        last edited by

        @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.

        1 Reply Last reply Reply Quote 1
        • NerdyDadN
          NerdyDad @travisdh1
          last edited by

          @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.

          scottalanmillerS 1 Reply Last reply Reply Quote 0
          • scottalanmillerS
            scottalanmiller @NerdyDad
            last edited by

            @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.

            NerdyDadN 1 Reply Last reply Reply Quote 0
            • NerdyDadN
              NerdyDad @scottalanmiller
              last edited by

              @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:

              1. How will this affect communications with my equipment when deployed and into production?
              2. What features does this add to the server? Better security?

              Definitely adds a layer of complexity to the mix.

              scottalanmillerS 1 Reply Last reply Reply Quote 0
              • scottalanmillerS
                scottalanmiller @NerdyDad
                last edited by

                @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:

                1. How will this affect communications with my equipment when deployed and into production?
                2. What features does this add to the server? Better security?

                Definitely adds a layer of complexity to the mix.

                But eliminate a complete server.

                NerdyDadN 1 Reply Last reply Reply Quote 0
                • scottalanmillerS
                  scottalanmiller
                  last edited by

                  @RojoLoco found out that we are talking about opening an Atlanta office.

                  1 Reply Last reply Reply Quote 0
                  • NerdyDadN
                    NerdyDad @scottalanmiller
                    last edited by

                    @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:

                    1. How will this affect communications with my equipment when deployed and into production?
                    2. 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?

                    scottalanmillerS 1 Reply Last reply Reply Quote 0
                    • DashrenderD
                      Dashrender @brianlittlejohn
                      last edited by

                      @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?

                      scottalanmillerS 1 Reply Last reply Reply Quote 0
                      • scottalanmillerS
                        scottalanmiller @NerdyDad
                        last edited by

                        @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:

                        1. How will this affect communications with my equipment when deployed and into production?
                        2. 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.

                        NerdyDadN 1 Reply Last reply Reply Quote 0
                        • scottalanmillerS
                          scottalanmiller @Dashrender
                          last edited by

                          @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

                          DashrenderD 1 Reply Last reply Reply Quote 1
                          • NerdyDadN
                            NerdyDad @scottalanmiller
                            last edited by

                            @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:

                            1. How will this affect communications with my equipment when deployed and into production?
                            2. 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?

                            ObsolesceO gjacobseG 4 Replies Last reply Reply Quote 0
                            • ObsolesceO
                              Obsolesce @NerdyDad
                              last edited by

                              @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:

                              1. How will this affect communications with my equipment when deployed and into production?
                              2. 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.

                              1 Reply Last reply Reply Quote 0
                              • DashrenderD
                                Dashrender @scottalanmiller
                                last edited by

                                @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.

                                scottalanmillerS 1 Reply Last reply Reply Quote 0
                                • ObsolesceO
                                  Obsolesce @NerdyDad
                                  last edited by

                                  @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:

                                  1. How will this affect communications with my equipment when deployed and into production?
                                  2. 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.

                                  1 Reply Last reply Reply Quote 0
                                  • ObsolesceO
                                    Obsolesce @NerdyDad
                                    last edited by

                                    @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:

                                    1. How will this affect communications with my equipment when deployed and into production?
                                    2. 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.

                                    1 Reply Last reply Reply Quote 0
                                    • scottalanmillerS
                                      scottalanmiller @Dashrender
                                      last edited by

                                      @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.

                                      1 Reply Last reply Reply Quote 0
                                      • scottalanmillerS
                                        scottalanmiller
                                        last edited by

                                        I've built seventeen servers on Vultr TODAY. lol

                                        ObsolesceO 1 Reply Last reply Reply Quote 1
                                        • scottalanmillerS
                                          scottalanmiller
                                          last edited by

                                          Rolling out another Fedora 26 desktop in the office. First of the Windows people considering converting.

                                          1 Reply Last reply Reply Quote 0
                                          • ObsolesceO
                                            Obsolesce @scottalanmiller
                                            last edited by

                                            @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?

                                            gjacobseG scottalanmillerS 2 Replies Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 2463
                                            • 2464
                                            • 2465
                                            • 2466
                                            • 2467
                                            • 4443
                                            • 4444
                                            • 2465 / 4444
                                            • First post
                                              Last post