SMS desktop app
-
@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 ?
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
-
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
-
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
@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. -
@timconsidine are there tried and true steps you do to setup certbot with ngoni every time?
@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.tlduntil I get responses. - I always do
nginx -tandsystemctl reload nginxto 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 -yOh, 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.
- I usually
-
@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.@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 -
@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.tlduntil I get responses. - I always do
nginx -tandsystemctl reload nginxto 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 -yOh, 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.
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!
- I usually
-
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!
-
@privsec cool, well done !
@timconsidine This also handles calls just fine
-
@timconsidine This also handles calls just fine
-
@timconsidine This also handles calls just fine
@privsec said in SMS desktop app:
@timconsidine This also handles calls just fine
that would be great for GVoice
-
@privsec said in SMS desktop app:
@timconsidine This also handles calls just fine
that would be great for GVoice
-
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?
-
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?
@privsec no haven't seen that, I will try and see what happens
-
@privsec no haven't seen that, I will try and see what happens
@timconsidine I am thinking there is something else wrong because even when using the website provided by operation privacy, I cant use the service.
-
@privsec no haven't seen that, I will try and see what happens
-
Out of curiosity, what node version does your lxc use? Mine defaults to 10.x.x
-
@privsec no haven't seen that, I will try and see what happens
@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-
Stopped the app running
ps aux | grep node
kill -9 xxxx (process number of running app) -
"backed up" the original installation by
mv VoIP/ VoIP-old/ -
Ran
git clone https://github.com/0perationPrivacy/VoIP.gitto create a new directory with latest version (0.89) -
Copied across settings from original deployment
cp VoIP-old/.env VoIP/.env -
Edited
VoIP/.envto add a new line at the end
HTTPS = false -
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.
-
-
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.
-
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.
@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 !
