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 21.3k 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.
  • 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
                            • P privsec

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

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

                              @privsec said in SMS desktop app:

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

                              maybe I am having a brain outage, but why are there 3 nginx files ?

                              P 1 Reply Last reply
                              0
                              • timconsidineT timconsidine

                                @privsec said in SMS desktop app:

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

                                maybe I am having a brain outage, but why are there 3 nginx files ?

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

                                @timconsidine

                                Well, I’m now unable to load the server. It seems that after the reboot I requested it is just frozen at the boot stage.

                                So I’m gonna have to start over.

                                However, I kept running into errors with certbot originally, until I made a .wellknown folder

                                P timconsidineT 2 Replies Last reply
                                0
                                • P privsec

                                  @timconsidine

                                  Well, I’m now unable to load the server. It seems that after the reboot I requested it is just frozen at the boot stage.

                                  So I’m gonna have to start over.

                                  However, I kept running into errors with certbot originally, until I made a .wellknown folder

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

                                  @timconsidine are there tried and true steps you do to setup certbot with ngoni every time?

                                  timconsidineT 1 Reply Last reply
                                  0
                                  • P privsec

                                    @timconsidine

                                    Well, I’m now unable to load the server. It seems that after the reboot I requested it is just frozen at the boot stage.

                                    So I’m gonna have to start over.

                                    However, I kept running into errors with certbot originally, until I made a .wellknown folder

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

                                    @privsec all those difficulties doesn't seem right to me

                                    What OS is on the VPS and what OS did you choose for the container ? (FYI on my installation it is Ubuntu 20.04 in both)

                                    Given that we are dealing with a container here (and that it's not working), I would trash the containers and start over from the top.
                                    lxc stop <container-name>
                                    lxc rm <container-name>

                                    Before creating the new container (can be same name as you used before if you prefer providing you remove it), I would make sure the VPS is up-to-date sudo apt-get update && sudo apt-get upgrade -y. And once the new container is created, I would do that same command again inside the new container.

                                    P 1 Reply Last reply
                                    0
                                    • P privsec

                                      @timconsidine are there tried and true steps you do to setup certbot with ngoni every time?

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

                                      @privsec said in SMS desktop app:

                                      @timconsidine are there tried and true steps you do to setup certbot with ngoni every time?

                                      I never have a problem with certbot except when I try to create a new certificate too soon after setting up the DNS, i.e. before it is propagated. To restrain my impatience :

                                      • I usually ping -c 5 sub.domain.tld until I get responses.
                                      • I always do nginx -t and systemctl reload nginx to ensure I get up-to-date nginx configs without any errors. Always have to resolve nginx errors before attempting a clean certbot certificate addition.

                                      If you are having nginx or certbot issues, I would make sure system is up to date with sudo apt-get update && sudo apt-get upgrade -y

                                      Oh, and be sure that all nginx and certbot work is done on the VPS, not while you are in the container.

                                      Feel free to ping me in chat if you wish to step through.

                                      P 1 Reply Last reply
                                      1
                                      • timconsidineT timconsidine

                                        @privsec all those difficulties doesn't seem right to me

                                        What OS is on the VPS and what OS did you choose for the container ? (FYI on my installation it is Ubuntu 20.04 in both)

                                        Given that we are dealing with a container here (and that it's not working), I would trash the containers and start over from the top.
                                        lxc stop <container-name>
                                        lxc rm <container-name>

                                        Before creating the new container (can be same name as you used before if you prefer providing you remove it), I would make sure the VPS is up-to-date sudo apt-get update && sudo apt-get upgrade -y. And once the new container is created, I would do that same command again inside the new container.

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

                                        @timconsidine said in SMS desktop app:

                                        sudo apt-get update && sudo apt-get upgrade -y

                                        I have wiped the VPS and started over.
                                        But both had the ubuntu 20.04 version

                                        1 Reply Last reply
                                        0
                                        • timconsidineT timconsidine

                                          @privsec said in SMS desktop app:

                                          @timconsidine are there tried and true steps you do to setup certbot with ngoni every time?

                                          I never have a problem with certbot except when I try to create a new certificate too soon after setting up the DNS, i.e. before it is propagated. To restrain my impatience :

                                          • I usually ping -c 5 sub.domain.tld until I get responses.
                                          • I always do nginx -t and systemctl reload nginx to ensure I get up-to-date nginx configs without any errors. Always have to resolve nginx errors before attempting a clean certbot certificate addition.

                                          If you are having nginx or certbot issues, I would make sure system is up to date with sudo apt-get update && sudo apt-get upgrade -y

                                          Oh, and be sure that all nginx and certbot work is done on the VPS, not while you are in the container.

                                          Feel free to ping me in chat if you wish to step through.

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

                                          @timconsidine

                                          Ok, I got this working by following your guide, then for lets encrypt, I followed https://haydenjames.io/how-to-set-up-an-nginx-certbot/up to step 4

                                          It is now live!

                                          timconsidineT 1 Reply Last reply
                                          3
                                          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