Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Off-topic
  3. SMS desktop app

SMS desktop app

Scheduled Pinned Locked Moved Off-topic
61 Posts 7 Posters 20.8k Views 8 Watching
  • 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.
  • timconsidineT timconsidine

    @privsec

    For LXC, can that be ran simultaneously on a cloudron server?

    well in theory I guess it could as LXC containers are separate from what else is going on in the VPS

    But I have a personal rule not to touch the Cloudron server other than through the Cloudron dashboard and the Cloudron CLI for custom apps. I don't log in to the VPS and don't do any maintenance on it. I just leave it all to Cloudron.

    I use another VPS from SSDNODES for 'experiments' and 'self-self-hosted' apps.

    S Offline
    S Offline
    subtlecourage
    wrote on last edited by
    #19

    sorry to revive this conversation, @privsec and @timconsidine, but how powerful of a server do you need?

    timconsidineT 2 Replies Last reply
    0
    • S subtlecourage

      sorry to revive this conversation, @privsec and @timconsidine, but how powerful of a server do you need?

      timconsidineT Offline
      timconsidineT Offline
      timconsidine
      App Dev
      wrote on last edited by
      #20

      @subtlecourage I don't think the project states minimum requirements.
      it's not a doing a lot, just a small mongodb and some api polling
      so I would guess a modest one
      nor more than 8gb ram and probably 4gb ram would be enough
      although that depends on what else is running on that VPS (remembering this app is in a container)

      S 1 Reply Last reply
      0
      • timconsidineT timconsidine

        @subtlecourage I don't think the project states minimum requirements.
        it's not a doing a lot, just a small mongodb and some api polling
        so I would guess a modest one
        nor more than 8gb ram and probably 4gb ram would be enough
        although that depends on what else is running on that VPS (remembering this app is in a container)

        S Offline
        S Offline
        subtlecourage
        wrote on last edited by
        #21

        @timconsidine thanks for the fast reply.

        Ok! Not a beefy one. I’m considering setting up these up for customers on an individual basis, and it seems a simple low tier server would be all that’s needed to run these.

        Probably a server with 20gb ram for multi number/family use cases would be appropriate.

        P 1 Reply Last reply
        0
        • S subtlecourage

          @timconsidine thanks for the fast reply.

          Ok! Not a beefy one. I’m considering setting up these up for customers on an individual basis, and it seems a simple low tier server would be all that’s needed to run these.

          Probably a server with 20gb ram for multi number/family use cases would be appropriate.

          P Offline
          P Offline
          privsec
          wrote on last edited by
          #22

          @subtlecourage that’s a neat idea, how would you offer support for that?

          1 Reply Last reply
          0
          • S subtlecourage

            sorry to revive this conversation, @privsec and @timconsidine, but how powerful of a server do you need?

            timconsidineT Offline
            timconsidineT Offline
            timconsidine
            App Dev
            wrote on last edited by timconsidine
            #23

            @subtlecourage here is the htop from the container

            Screenshot 2021-11-02 at 13.05.45.png
            Not much going on

            P 2 Replies Last reply
            1
            • timconsidineT timconsidine

              It's also particularly useful for international usage.
              E.g. I am in Ukraine now, and it is exorbitant to send SMS back to the UK (inbound to me is free but replying is <ouch>, especially MMS if that is needed).
              I have used a virtual number service (Hushed) but it's not cheap either, and ties you to their number and renewing it.
              The Telnyx platform gives me outbound SMS for normal rates and cheap number rental. Even posisble to load up multiple numbers (one for sales, one for support, one for personal) without breaking the bank.
              [OK, it's not in my phone unlimited SMS package, but still much more affordable.]

              scookeS Offline
              scookeS Offline
              scooke
              wrote on last edited by
              #24

              @timconsidine said in SMS desktop app:

              virtual number service (Hushed) but it's not cheap

              Hushed is one sale at:
              https://www.groupon.com/deals/hushed-com-nat-2
              https://stacksocial.com/sales/hushed-private-phone-1-line-plan-1000-mins-6000-sms (I bought a Lifetime plan from StackSocial 5+ years ago)

              This last one is Hushed bundled with Keep Solid VPN Unlimited (I've been using both for 5+ years with good success):
              https://stacksocial.com/sales/the-lifetime-mobile-privacy-security-subscription-bundle-hushed

              I guess since it's been 5+ years you can count on the service to last, and not bait-and-switch after a year.

              A life lived in fear is a life half-lived

              P 1 Reply Last reply
              1
              • timconsidineT timconsidine

                I was about to post this in AppWishlist but realised that the underlying app is still in beta, so too early for a Cloudron instance.

                However I think it can be of great interest to self-hosters.

                There are many commercial services where you can send SMS out and receive responses back in for customer support or marketing enquiries. An alternative channel to email and website chat channels, or social media channels. But the commercial services are not cheap, and you are tied to their numbers (lock in).

                So I was pleased to discover while doing OSINT research that there is a self-hosted system in development, to use virtual numbers from Telnyx (or Twilio).

                There is also a small privacy element that you can text in/out without a phone's location being tracked, if you want it for personal not commercial use.

                The self-hosting documentation is patchy, so I created my own HOW-TO : https://github.com/timconsidine/LXC-OperationPrivacy-VOIP

                It has the links to the underlying repo.

                Just in case it helps anyone here.

                L Offline
                L Offline
                LoudLemur
                wrote on last edited by
                #25

                @timconsidine There is an SMS module in Odoo / Flectra, which might have some functionality you need. Odoo and Flectra are in the wishlist:

                https://www.odoo.com/app/sms-marketing

                timconsidineT 1 Reply Last reply
                1
                • L LoudLemur

                  @timconsidine There is an SMS module in Odoo / Flectra, which might have some functionality you need. Odoo and Flectra are in the wishlist:

                  https://www.odoo.com/app/sms-marketing

                  timconsidineT Offline
                  timconsidineT Offline
                  timconsidine
                  App Dev
                  wrote on last edited by
                  #26

                  @loudlemur thanks, but I don't need oodo / flectra

                  1 Reply Last reply
                  0
                  • scookeS scooke

                    @timconsidine said in SMS desktop app:

                    virtual number service (Hushed) but it's not cheap

                    Hushed is one sale at:
                    https://www.groupon.com/deals/hushed-com-nat-2
                    https://stacksocial.com/sales/hushed-private-phone-1-line-plan-1000-mins-6000-sms (I bought a Lifetime plan from StackSocial 5+ years ago)

                    This last one is Hushed bundled with Keep Solid VPN Unlimited (I've been using both for 5+ years with good success):
                    https://stacksocial.com/sales/the-lifetime-mobile-privacy-security-subscription-bundle-hushed

                    I guess since it's been 5+ years you can count on the service to last, and not bait-and-switch after a year.

                    P Offline
                    P Offline
                    privsec
                    wrote on last edited by
                    #27

                    @scooke
                    The issue with apps like these is their privacy priactices

                    ) Usage Information
                    i. like most website and app operators, we collect information about your interactions with the Services, such as which screens or pages you visit, what you click on, when you perform those actions, language preferences, and so on);
                    ii. message content contained within SMS/MMS segments as well as the source and destination numbers are stored until you delete your message history, associated phone number, or your account;
                    iii. CDR (Call Detail Records) are stored until you delete the call log, associated phone number, or your account (CDRs contains various attributes of the call, such as time, duration, completion status, source number, and destination number);
                    iv. voicemail recordings and voicemail greetings are stored until you delete voicemail recordings, voicemail greetings, the associated phone number, or your account; and
                    v. You are entirely and solely responsible for any information that you disclose or share with other users through our Services. We strongly recommend that you use extreme caution in sharing any personal information with other parties through our Services – AffinityClick is not responsible for any information that you disclose to other parties through our Services.
                    
                    e) Information from Third Parties and Integration Partners
                    i. we collect your information or data from third parties if you give permission to those third parties to share your information with us or where you have made that information publicly available online (e.g. if you enable service integrations with DropBox or Slack, they may send us your information which they have collected, all of which will be controlled by such third party); and
                    **ii. other sources (to the extent permitted by applicable law we may receive additional information about you, such as demographic data or fraud detection information and warnings, or other information about you from partner networks).**
                    

                    And

                    f) Log Data
                    i. we collect log data each time a device accesses our servers, log data includes details about the nature of each access including originating IP addresses, access times, device type, operating system versions, internet service providers, pages you view before and after using the Services, links to third party applications, and hardware and software information.
                    

                    The benefits of this self hosted service is you control pretty much everything.

                    1 Reply Last reply
                    0
                    • timconsidineT timconsidine

                      @subtlecourage here is the htop from the container

                      Screenshot 2021-11-02 at 13.05.45.png
                      Not much going on

                      P Offline
                      P Offline
                      privsec
                      wrote on last edited by
                      #28

                      @timconsidine said in SMS desktop app:

                      htop

                      WOW!! I think @subtlecourage has the right idea here about offering this as a potential service.

                      The load on this machine is minuscule.

                      So question, the RAM usage, it appears to be megabytes, does that correlate with the size of the DB?

                      Or will it pretty much stay below 250mbs?

                      Because based off of that, you really don't need even a modest machine. It looks like you could run this on a potato.

                      1 Reply Last reply
                      1
                      • timconsidineT timconsidine

                        @subtlecourage here is the htop from the container

                        Screenshot 2021-11-02 at 13.05.45.png
                        Not much going on

                        P Offline
                        P Offline
                        privsec
                        wrote on last edited by
                        #29

                        @timconsidine

                        I am running into an issue with issue a cert from certbot.

                        First, I have never manually issued a cert from certbot before nor have I have nginx before.

                        So this is all a learning curve.

                        Below is my code

                        sudo certbot certonly
                        Saving debug log to /var/log/letsencrypt/letsencrypt.log
                        
                        How would you like to authenticate with the ACME CA?
                        - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                        1: Spin up a temporary webserver (standalone)
                        2: Place files in webroot directory (webroot)
                        - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                        Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2
                        Plugins selected: Authenticator webroot, Installer None
                        Enter email address (used for urgent renewal and security notices) (Enter 'c' to
                        cancel): letsencrypt@domain.com
                        
                        - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                        Please read the Terms of Service at
                        https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf. You must
                        agree in order to register with the ACME server at
                        https://acme-v02.api.letsencrypt.org/directory
                        - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                        (A)gree/(C)ancel: A
                        
                        - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                        Would you be willing to share your email address with the Electronic Frontier
                        Foundation, a founding partner of the Let's Encrypt project and the non-profit
                        organization that develops Certbot? We'd like to send you email about our work
                        encrypting the web, EFF news, campaigns, and ways to support digital freedom.
                        - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                        (Y)es/(N)o: N
                        Please enter in your domain name(s) (comma and/or space separated)  (Enter 'c'
                        to cancel): domain.com, 2.domain.com
                        
                        Obtaining a new certificate
                        Performing the following challenges:
                        http-01 challenge for domain.com http-01 challenge for 2.domain.com
                        
                        Input the webroot for domain.com
                        : (Enter 'c' to cancel): /var/www/letsencrypt/.well-known/acme-challenge/
                        
                        - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                        /var/www/letsencrypt/.well-known/acme-challenge/ does not exist or is not a
                        directory
                        - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                        Input the webroot for domain.com: (Enter 'c' to cancel): sudo mkdir /var/www/letsencrypt/.well-known/acme-challenge/
                        
                        - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                        sudo mkdir /var/www/letsencrypt/.well-known/acme-challenge/ does not exist or is
                        not a directory
                        - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                        Input the webroot for domain.com: (Enter 'c' to cancel): /var/www/
                        
                        Select the webroot for 2.domain.com:
                        - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                        1: Enter a new webroot
                        2: /var/www
                        - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                        Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2
                        Waiting for verification...
                        Challenge failed for domain domain.com
                        Challenge failed for domain 2.domain.com
                        http-01 challenge for domain.com
                        http-01 challenge for 2.domain.com
                        Cleaning up challenges
                        Some challenges have failed.
                        
                        IMPORTANT NOTES:
                         - The following errors were reported by the server:
                        
                           Domain: domain.com
                           Type:   dns
                           Detail: No valid IP addresses found for domain.com
                         - The following errors were reported by the server:
                        
                           Domain: 2.domain.com
                           Type:   unauthorized
                           Detail: Invalid response from
                           http://2.domain.com/.well-known/acme-challenge/I0MKBgfBDsVANUdgpJpNkwAttlex9oev_DXaWCveCbU
                           [ip.add.re.ss]: "<html>\r\n<head><title>404 Not
                           Found</title></head>\r\n<body>\r\n<center><h1>404 Not
                           Found</h1></center>\r\n<hr><center>nginx/1.18.0 (Ub"
                        
                           To fix these errors, please make sure that your domain name was
                           entered correctly and the DNS A/AAAA record(s) for that domain
                           contain(s) the right IP address.
                         - Your account credentials have been saved in your Certbot
                           configuration directory at /etc/letsencrypt. You should make a
                           secure backup of this folder now. This configuration directory will
                           also contain certificates and private keys obtained by Certbot so
                           making regular backups of this folder is ideal.
                        obfuscateduser:~/VoIP$ 2.domain.com
                        
                        

                        My domain settings are like so

                        6d802fdc-0836-40be-9664-2e357532ce45-image.png

                        My /etc/nginx/sites-available/<domain>.<tld> file looks like

                        91d0dbb0-fda2-43d5-a42d-304967433c3c-image.png

                        Your help/guidance would be greatly appreciated

                        P timconsidineT 2 Replies Last reply
                        0
                        • P privsec

                          @timconsidine

                          I am running into an issue with issue a cert from certbot.

                          First, I have never manually issued a cert from certbot before nor have I have nginx before.

                          So this is all a learning curve.

                          Below is my code

                          sudo certbot certonly
                          Saving debug log to /var/log/letsencrypt/letsencrypt.log
                          
                          How would you like to authenticate with the ACME CA?
                          - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                          1: Spin up a temporary webserver (standalone)
                          2: Place files in webroot directory (webroot)
                          - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                          Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2
                          Plugins selected: Authenticator webroot, Installer None
                          Enter email address (used for urgent renewal and security notices) (Enter 'c' to
                          cancel): letsencrypt@domain.com
                          
                          - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                          Please read the Terms of Service at
                          https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf. You must
                          agree in order to register with the ACME server at
                          https://acme-v02.api.letsencrypt.org/directory
                          - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                          (A)gree/(C)ancel: A
                          
                          - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                          Would you be willing to share your email address with the Electronic Frontier
                          Foundation, a founding partner of the Let's Encrypt project and the non-profit
                          organization that develops Certbot? We'd like to send you email about our work
                          encrypting the web, EFF news, campaigns, and ways to support digital freedom.
                          - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                          (Y)es/(N)o: N
                          Please enter in your domain name(s) (comma and/or space separated)  (Enter 'c'
                          to cancel): domain.com, 2.domain.com
                          
                          Obtaining a new certificate
                          Performing the following challenges:
                          http-01 challenge for domain.com http-01 challenge for 2.domain.com
                          
                          Input the webroot for domain.com
                          : (Enter 'c' to cancel): /var/www/letsencrypt/.well-known/acme-challenge/
                          
                          - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                          /var/www/letsencrypt/.well-known/acme-challenge/ does not exist or is not a
                          directory
                          - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                          Input the webroot for domain.com: (Enter 'c' to cancel): sudo mkdir /var/www/letsencrypt/.well-known/acme-challenge/
                          
                          - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                          sudo mkdir /var/www/letsencrypt/.well-known/acme-challenge/ does not exist or is
                          not a directory
                          - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                          Input the webroot for domain.com: (Enter 'c' to cancel): /var/www/
                          
                          Select the webroot for 2.domain.com:
                          - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                          1: Enter a new webroot
                          2: /var/www
                          - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                          Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2
                          Waiting for verification...
                          Challenge failed for domain domain.com
                          Challenge failed for domain 2.domain.com
                          http-01 challenge for domain.com
                          http-01 challenge for 2.domain.com
                          Cleaning up challenges
                          Some challenges have failed.
                          
                          IMPORTANT NOTES:
                           - The following errors were reported by the server:
                          
                             Domain: domain.com
                             Type:   dns
                             Detail: No valid IP addresses found for domain.com
                           - The following errors were reported by the server:
                          
                             Domain: 2.domain.com
                             Type:   unauthorized
                             Detail: Invalid response from
                             http://2.domain.com/.well-known/acme-challenge/I0MKBgfBDsVANUdgpJpNkwAttlex9oev_DXaWCveCbU
                             [ip.add.re.ss]: "<html>\r\n<head><title>404 Not
                             Found</title></head>\r\n<body>\r\n<center><h1>404 Not
                             Found</h1></center>\r\n<hr><center>nginx/1.18.0 (Ub"
                          
                             To fix these errors, please make sure that your domain name was
                             entered correctly and the DNS A/AAAA record(s) for that domain
                             contain(s) the right IP address.
                           - Your account credentials have been saved in your Certbot
                             configuration directory at /etc/letsencrypt. You should make a
                             secure backup of this folder now. This configuration directory will
                             also contain certificates and private keys obtained by Certbot so
                             making regular backups of this folder is ideal.
                          obfuscateduser:~/VoIP$ 2.domain.com
                          
                          

                          My domain settings are like so

                          6d802fdc-0836-40be-9664-2e357532ce45-image.png

                          My /etc/nginx/sites-available/<domain>.<tld> file looks like

                          91d0dbb0-fda2-43d5-a42d-304967433c3c-image.png

                          Your help/guidance would be greatly appreciated

                          P Offline
                          P Offline
                          privsec
                          wrote on last edited by
                          #30

                          I have tried blindly following along the nginx steps in the guide as well as https://www.nginx.com/blog/using-free-ssltls-certificates-from-lets-encrypt-with-nginx/

                          And neither are working

                          P 1 Reply Last reply
                          0
                          • P privsec

                            I have tried blindly following along the nginx steps in the guide as well as https://www.nginx.com/blog/using-free-ssltls-certificates-from-lets-encrypt-with-nginx/

                            And neither are working

                            P Offline
                            P Offline
                            privsec
                            wrote on last edited by
                            #31

                            Hooray! After blindly throwing things at the wall, the command sudo apt-get install python3-certbot-nginx moved me along.

                            Now my domain name is redirecting me to a bad gteway page. Progress.

                            P 1 Reply Last reply
                            0
                            • P privsec

                              Hooray! After blindly throwing things at the wall, the command sudo apt-get install python3-certbot-nginx moved me along.

                              Now my domain name is redirecting me to a bad gteway page. Progress.

                              P Offline
                              P Offline
                              privsec
                              wrote on last edited by
                              #32

                              Ok, so, another problem

                              Within the LXC container, I cant resolve to any external providers. 57adeff6-f9b0-4004-a0ce-b02868c2dc11-image.png

                              And not surprisingly, installing everything outside the container does nothing.

                              But to be clear, within the container, nothing works or install able, outside of the LXC container, it all works.

                              P 1 Reply Last reply
                              0
                              • P privsec

                                Ok, so, another problem

                                Within the LXC container, I cant resolve to any external providers. 57adeff6-f9b0-4004-a0ce-b02868c2dc11-image.png

                                And not surprisingly, installing everything outside the container does nothing.

                                But to be clear, within the container, nothing works or install able, outside of the LXC container, it all works.

                                P Offline
                                P Offline
                                privsec
                                wrote on last edited by
                                #33

                                Ok, I have determined that it was my UFW firewall rules

                                1 Reply Last reply
                                2
                                • P privsec

                                  @timconsidine

                                  I am running into an issue with issue a cert from certbot.

                                  First, I have never manually issued a cert from certbot before nor have I have nginx before.

                                  So this is all a learning curve.

                                  Below is my code

                                  sudo certbot certonly
                                  Saving debug log to /var/log/letsencrypt/letsencrypt.log
                                  
                                  How would you like to authenticate with the ACME CA?
                                  - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                  1: Spin up a temporary webserver (standalone)
                                  2: Place files in webroot directory (webroot)
                                  - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                  Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2
                                  Plugins selected: Authenticator webroot, Installer None
                                  Enter email address (used for urgent renewal and security notices) (Enter 'c' to
                                  cancel): letsencrypt@domain.com
                                  
                                  - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                  Please read the Terms of Service at
                                  https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf. You must
                                  agree in order to register with the ACME server at
                                  https://acme-v02.api.letsencrypt.org/directory
                                  - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                  (A)gree/(C)ancel: A
                                  
                                  - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                  Would you be willing to share your email address with the Electronic Frontier
                                  Foundation, a founding partner of the Let's Encrypt project and the non-profit
                                  organization that develops Certbot? We'd like to send you email about our work
                                  encrypting the web, EFF news, campaigns, and ways to support digital freedom.
                                  - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                  (Y)es/(N)o: N
                                  Please enter in your domain name(s) (comma and/or space separated)  (Enter 'c'
                                  to cancel): domain.com, 2.domain.com
                                  
                                  Obtaining a new certificate
                                  Performing the following challenges:
                                  http-01 challenge for domain.com http-01 challenge for 2.domain.com
                                  
                                  Input the webroot for domain.com
                                  : (Enter 'c' to cancel): /var/www/letsencrypt/.well-known/acme-challenge/
                                  
                                  - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                  /var/www/letsencrypt/.well-known/acme-challenge/ does not exist or is not a
                                  directory
                                  - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                  Input the webroot for domain.com: (Enter 'c' to cancel): sudo mkdir /var/www/letsencrypt/.well-known/acme-challenge/
                                  
                                  - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                  sudo mkdir /var/www/letsencrypt/.well-known/acme-challenge/ does not exist or is
                                  not a directory
                                  - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                  Input the webroot for domain.com: (Enter 'c' to cancel): /var/www/
                                  
                                  Select the webroot for 2.domain.com:
                                  - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                  1: Enter a new webroot
                                  2: /var/www
                                  - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                  Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2
                                  Waiting for verification...
                                  Challenge failed for domain domain.com
                                  Challenge failed for domain 2.domain.com
                                  http-01 challenge for domain.com
                                  http-01 challenge for 2.domain.com
                                  Cleaning up challenges
                                  Some challenges have failed.
                                  
                                  IMPORTANT NOTES:
                                   - The following errors were reported by the server:
                                  
                                     Domain: domain.com
                                     Type:   dns
                                     Detail: No valid IP addresses found for domain.com
                                   - The following errors were reported by the server:
                                  
                                     Domain: 2.domain.com
                                     Type:   unauthorized
                                     Detail: Invalid response from
                                     http://2.domain.com/.well-known/acme-challenge/I0MKBgfBDsVANUdgpJpNkwAttlex9oev_DXaWCveCbU
                                     [ip.add.re.ss]: "<html>\r\n<head><title>404 Not
                                     Found</title></head>\r\n<body>\r\n<center><h1>404 Not
                                     Found</h1></center>\r\n<hr><center>nginx/1.18.0 (Ub"
                                  
                                     To fix these errors, please make sure that your domain name was
                                     entered correctly and the DNS A/AAAA record(s) for that domain
                                     contain(s) the right IP address.
                                   - Your account credentials have been saved in your Certbot
                                     configuration directory at /etc/letsencrypt. You should make a
                                     secure backup of this folder now. This configuration directory will
                                     also contain certificates and private keys obtained by Certbot so
                                     making regular backups of this folder is ideal.
                                  obfuscateduser:~/VoIP$ 2.domain.com
                                  
                                  

                                  My domain settings are like so

                                  6d802fdc-0836-40be-9664-2e357532ce45-image.png

                                  My /etc/nginx/sites-available/<domain>.<tld> file looks like

                                  91d0dbb0-fda2-43d5-a42d-304967433c3c-image.png

                                  Your help/guidance would be greatly appreciated

                                  timconsidineT Offline
                                  timconsidineT Offline
                                  timconsidine
                                  App Dev
                                  wrote on last edited by
                                  #34

                                  @privsec sorry I missed this.
                                  all working now ?

                                  P 2 Replies Last reply
                                  0
                                  • timconsidineT timconsidine

                                    @privsec sorry I missed this.
                                    all working now ?

                                    P Offline
                                    P Offline
                                    privsec
                                    wrote on last edited by
                                    #35

                                    @timconsidine

                                    No worries!

                                    Sadly, no.

                                    I finally have b5becb25-e1a4-4b5a-abef-79491214140c-image.png
                                    in my terminal via the LXC, but in my browser, all I am getting is
                                    36c981b9-6f89-443d-b292-c1ec7799f1b3-image.png

                                    timconsidineT 1 Reply Last reply
                                    0
                                    • timconsidineT timconsidine

                                      @privsec sorry I missed this.
                                      all working now ?

                                      P Offline
                                      P Offline
                                      privsec
                                      wrote on last edited by
                                      #36

                                      @timconsidine

                                      These are my logs

                                      2021/11/03 13:17:06 [error] 47695#47695: *14 connect() failed (111: Connection refused) while connecting to upstream, client: xx.xx.xx.xx, server: app.domain.com, request: "GET / HTTP/1.1", up>
                                      2021/11/03 13:17:06 [error] 47695#47695: *14 connect() failed (111: Connection refused) while connecting to upstream, client: xx.xx.xx.xx,, server: app.domain.com, request: "GET /favicon.ico HT>
                                      2021/11/03 13:17:27 [error] 47695#47695: *19 connect() failed (111: Connection refused) while connecting to upstream, client: xx.xx.xx.xx,, server: app.domain.com, request: "GET / HTTP/1.1", u>
                                      2021/11/03 13:17:27 [error] 47695#47695: *23 connect() failed (111: Connection refused) while connecting to upstream, client: xx.xx.xx.xx,, server: app.domain.com, request: "GET / HTTP/1.1", u>
                                      2021/11/03 13:17:27 [error] 47695#47695: *24 connect() failed (111: Connection refused) while connecting to upstream, client: xx.xx.xx.xx,, server: app.domain.com, request: "GET / HTTP/1.1", u>
                                      2021/11/03 13:17:59 [error] 47695#47695: *27 connect() failed (111: Connection refused) while connecting to upstream, client: xx.xx.xx.xx,, server: app.domain.com, request: "GET / HTTP/1.1", u>
                                      2021/11/03 13:19:08 [error] 47695#47695: *29 connect() failed (111: Connection refused) while connecting to upstream, client: xx.xx.xx.xx,, server: app.domain.com, request: "GET / HTTP/1.1", u>
                                      2021/11/03 13:22:47 [warn] 48507#48507: conflicting server name "app.domain.com" on 0.0.0.0:80, ignored
                                      2021/11/03 13:22:47 [warn] 48507#48507: conflicting server name "app.domain.com" on [::]:80, ignored
                                      2021/11/03 13:23:14 [warn] 48554#48554: conflicting server name "app.domain.com" on 0.0.0.0:80, ignored
                                      2021/11/03 13:23:14 [warn] 48554#48554: conflicting server name "app.domain.com" on [::]:80, ignored
                                      
                                      
                                      P 1 Reply Last reply
                                      0
                                      • P privsec

                                        @timconsidine

                                        These are my logs

                                        2021/11/03 13:17:06 [error] 47695#47695: *14 connect() failed (111: Connection refused) while connecting to upstream, client: xx.xx.xx.xx, server: app.domain.com, request: "GET / HTTP/1.1", up>
                                        2021/11/03 13:17:06 [error] 47695#47695: *14 connect() failed (111: Connection refused) while connecting to upstream, client: xx.xx.xx.xx,, server: app.domain.com, request: "GET /favicon.ico HT>
                                        2021/11/03 13:17:27 [error] 47695#47695: *19 connect() failed (111: Connection refused) while connecting to upstream, client: xx.xx.xx.xx,, server: app.domain.com, request: "GET / HTTP/1.1", u>
                                        2021/11/03 13:17:27 [error] 47695#47695: *23 connect() failed (111: Connection refused) while connecting to upstream, client: xx.xx.xx.xx,, server: app.domain.com, request: "GET / HTTP/1.1", u>
                                        2021/11/03 13:17:27 [error] 47695#47695: *24 connect() failed (111: Connection refused) while connecting to upstream, client: xx.xx.xx.xx,, server: app.domain.com, request: "GET / HTTP/1.1", u>
                                        2021/11/03 13:17:59 [error] 47695#47695: *27 connect() failed (111: Connection refused) while connecting to upstream, client: xx.xx.xx.xx,, server: app.domain.com, request: "GET / HTTP/1.1", u>
                                        2021/11/03 13:19:08 [error] 47695#47695: *29 connect() failed (111: Connection refused) while connecting to upstream, client: xx.xx.xx.xx,, server: app.domain.com, request: "GET / HTTP/1.1", u>
                                        2021/11/03 13:22:47 [warn] 48507#48507: conflicting server name "app.domain.com" on 0.0.0.0:80, ignored
                                        2021/11/03 13:22:47 [warn] 48507#48507: conflicting server name "app.domain.com" on [::]:80, ignored
                                        2021/11/03 13:23:14 [warn] 48554#48554: conflicting server name "app.domain.com" on 0.0.0.0:80, ignored
                                        2021/11/03 13:23:14 [warn] 48554#48554: conflicting server name "app.domain.com" on [::]:80, ignored
                                        
                                        
                                        P Offline
                                        P Offline
                                        privsec
                                        wrote on last edited by
                                        #37

                                        @privsec
                                        I have confirmed that the all three nginx files use the LXC IP address, not the VPS IP address.

                                        timconsidineT 1 Reply Last reply
                                        0
                                        • P privsec

                                          @timconsidine

                                          No worries!

                                          Sadly, no.

                                          I finally have b5becb25-e1a4-4b5a-abef-79491214140c-image.png
                                          in my terminal via the LXC, but in my browser, all I am getting is
                                          36c981b9-6f89-443d-b292-c1ec7799f1b3-image.png

                                          timconsidineT Offline
                                          timconsidineT Offline
                                          timconsidine
                                          App Dev
                                          wrote on last edited by timconsidine
                                          #38

                                          @privsec it does take a moment or two before starting up
                                          but if this persists, seems like it is not finding the app

                                          at the risk of basics for troubleshooting:

                                          • inside the container and inside the installation directory, you have done node app.js & to start it (I have forgotten a couple of times). I think you have because you got database connected but maybe the program stopped for some other change

                                          • outside the container, you have run systemctl reload nginx without errors ? and/or run nginx -t without errors ?

                                          • these errors suggest continuing nginx conf issue

                                          2021/11/03 13:22:47 [warn] 48507#48507: conflicting server name "app.domain.com" on 0.0.0.0:80, ignored
                                          2021/11/03 13:22:47 [warn] 48507#48507: conflicting server name "app.domain.com" on [::]:80, ignored
                                          2021/11/03 13:23:14 [warn] 48554#48554: conflicting server name "app.domain.com" on 0.0.0.0:80, ignored
                                          2021/11/03 13:23:14 [warn] 48554#48554: conflicting server name "app.domain.com" on [::]:80, ignored
                                          

                                          what is latest / current nginx conf file ?

                                          1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          • Login

                                          • Don't have an account? Register

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular
                                          • Bookmarks
                                          • Search