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


    Cloudron Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    SMS desktop app

    Off-topic
    7
    61
    3451
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P
      privsec @privsec last edited by

      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 Reply Quote 0
      • P
        privsec @privsec last edited by

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

        1 Reply Last reply Reply Quote 2
        • timconsidine
          timconsidine @privsec last edited by

          @privsec sorry I missed this.
          all working now ?

          P 2 Replies Last reply Reply Quote 0
          • P
            privsec @timconsidine last edited by

            @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

            timconsidine 1 Reply Last reply Reply Quote 0
            • P
              privsec @timconsidine last edited by

              @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 Reply Quote 0
              • P
                privsec @privsec last edited by

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

                timconsidine 1 Reply Last reply Reply Quote 0
                • timconsidine
                  timconsidine @privsec last edited by timconsidine

                  @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 Reply Quote 0
                  • timconsidine
                    timconsidine @privsec last edited by

                    @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 Reply Quote 0
                    • P
                      privsec @timconsidine last edited by

                      @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 timconsidine 2 Replies Last reply Reply Quote 0
                      • P
                        privsec @privsec last edited by

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

                        timconsidine 1 Reply Last reply Reply Quote 0
                        • timconsidine
                          timconsidine @privsec last edited by 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 1 Reply Last reply Reply Quote 0
                          • timconsidine
                            timconsidine @privsec last edited by

                            @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 Reply Quote 1
                            • P
                              privsec @timconsidine last edited by

                              @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 Reply Quote 0
                              • P
                                privsec @timconsidine last edited by privsec

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

                                timconsidine 1 Reply Last reply Reply Quote 3
                                • timconsidine
                                  timconsidine @privsec last edited by

                                  @privsec cool, well done !

                                  P 1 Reply Last reply Reply Quote 0
                                  • P
                                    privsec @timconsidine last edited by

                                    @timconsidine This also handles calls just fine

                                    timconsidine robi 2 Replies Last reply Reply Quote 1
                                    • timconsidine
                                      timconsidine @privsec last edited by

                                      @privsec : hadn't tested yet, thanks for doing that !

                                      1 Reply Last reply Reply Quote 0
                                      • robi
                                        robi @privsec last edited by

                                        @privsec said in SMS desktop app:

                                        @timconsidine This also handles calls just fine

                                        that would be great for GVoice

                                        Life of Advanced Technology

                                        P 1 Reply Last reply Reply Quote 0
                                        • P
                                          privsec @robi last edited by

                                          @robi Currently, the app only allows for Telnyx or a Twilio API key.

                                          Does GVoice use an API key?

                                          1 Reply Last reply Reply Quote 0
                                          • P
                                            privsec last edited by privsec

                                            So I was doing some thinking on this, and couldn’t one set up several cron jobs to do the following weekly

                                            • kill all node
                                            • merge the currently cloned repo with the new repo (updates, fixes, bugs)
                                            • restart app
                                            1 Reply Last reply Reply Quote 0
                                            • P
                                              privsec last edited by

                                              @timconsidine

                                              Are you getting any error messages when you attempt to update the app with the github repo?

                                              When I do, I am getting an error message about node dependencies that I havent gotten before.

                                              I have tried various PPAs of NodeJS and NPM and I still get

                                              E: Unable to correct problems, you have held broken packages.

                                              Any ideas on this one?

                                              timconsidine 1 Reply Last reply Reply Quote 0
                                              • timconsidine
                                                timconsidine @privsec last edited by

                                                @privsec no haven't seen that, I will try and see what happens

                                                P timconsidine 3 Replies Last reply Reply Quote 0
                                                • P
                                                  privsec @timconsidine last edited by

                                                  @timconsidine I am thinking there is something else wrong because even when using the website provided by operation privacy, I cant use the service.

                                                  1 Reply Last reply Reply Quote 0
                                                  • P
                                                    privsec @timconsidine last edited by

                                                    @timconsidine

                                                    Out of curiosity, what node version does your lxc use? Mine defaults to 10.x.x

                                                    timconsidine 1 Reply Last reply Reply Quote 0
                                                    • timconsidine
                                                      timconsidine @privsec last edited by

                                                      @privsec sorry I missed this question
                                                      Yes, mine is running 10.x.x

                                                      1 Reply Last reply Reply Quote 0
                                                      • timconsidine
                                                        timconsidine @timconsidine last edited by

                                                        @timconsidine in case anyone is interested, updating the app in the LXC container is fairly straight-forward.
                                                        I held off for a long time, but eventually bit the bullet.

                                                        The steps I took are a bit manual / kludge but it was fastest way.
                                                        This assumes you are in root directory of container/installation

                                                        1. Stopped the app running
                                                          ps aux | grep node
                                                          kill -9 xxxx (process number of running app)

                                                        2. "backed up" the original installation by mv VoIP/ VoIP-old/

                                                        3. Ran git clone https://github.com/0perationPrivacy/VoIP.git to create a new directory with latest version (0.89)

                                                        4. Copied across settings from original deployment
                                                          cp VoIP-old/.env VoIP/.env

                                                        5. Edited VoIP/.env to add a new line at the end
                                                          HTTPS = false

                                                        6. Started app
                                                          cd VoIP/
                                                          node app.js &

                                                        This kept all settings (database, domain) and also all data (contacts, messages).

                                                        Not extensively tested but it seems to be running ok.

                                                        1 Reply Last reply Reply Quote 1
                                                        • K
                                                          katerynajohnson last edited by katerynajohnson

                                                          Once I tried to create sms desktop app but it didn't work out...Thus, every time when I need a solution I google on the web https://www.google.com/ and search fresh options.

                                                          timconsidine 1 Reply Last reply Reply Quote 0
                                                          • timconsidine
                                                            timconsidine @katerynajohnson last edited by

                                                            @katerynajohnson do you mean THIS particular app didn't work ? Or some other one generally ?

                                                            If you need help to install it, I can maybe advise you.
                                                            This particular app has not been built for Cloudron.
                                                            I'm still looking into whether that is possible.
                                                            In its current form, it can be deployed on any linux VPS as an LXC container.

                                                            Use www.google.com ? NEVER !! 😆
                                                            duckduckgo.com or ecosia or start page .... or your own Searx available on Cloudron !

                                                            L 1 Reply Last reply Reply Quote 1
                                                            • L
                                                              LoudLemur @timconsidine last edited by

                                                              @timconsidine
                                                              https://www.seekr.com/ is cool, but proprietary. I would prefer it over DDG. The results are good too.

                                                              timconsidine 1 Reply Last reply Reply Quote 0
                                                              • timconsidine
                                                                timconsidine @LoudLemur last edited by

                                                                @LoudLemur .... but they have marketing driven cookies

                                                                1 Reply Last reply Reply Quote 1
                                                                • First post
                                                                  Last post
                                                                Powered by NodeBB