Postcards for SMS by Skyetel.
-
@Skyetel said in Postcards for SMS by Skyetel.:
We went with docker to maintain that standard, but it has created some headaches for our users who aren't comfortable with it.
As long as it is all automated, and you publish all the requirements, it's not too bad. Unnecessarily complex, but not bad. The issue above was only that the existence of Docker created more confusion when the actual issue was just that the Docker install script appears to be Ubuntu-only and doesn't support CentOS.
-
FYI: - I AM running with Centos 7 - successfully - and you are now addressing several of our concerns.
One thing we really want to see in the new version that I don't see listed is the option to have user .. then if user1 replies to one message and user2 replies to the next... we know who did what.
-
Nicht sehr gut.
Ubuntu installed in a breeze.
Postcards installed almost as easy, had to install some pre-requisites.
Skyetel setup went fine.In the bowser......
500 Internal Server Error __________________ nginx/1.17.6 -
Well, I guess this is where I start being forced to learn about Docker. I am getting an nginx 500 error, but nginx is not installed in my OS. Is it hiding inside a container? How do I get to it?
-
I'm inside the docker.... going deep now!
-
http://<ipaddress> brings up the user login to Postcards.
https://<ipaddress>/backend/admin returns the 500 error. Could it be a boogered up LE cert?
-
I haven't looked at their install script in a while, but for sure there was a LE issue. Here's a copy of my note to Skyetel regarding the issue. I thought the script had been updated with our patch, but here it is in case not:
FYI - we've resolved the issue, and I can only assume anyone else that has installed Postcards should have the same issue.
The problem is indeed an issue with Let's Encrypt, and specifically:
docker: jrcs/letsencrypt-nginx-proxy-companion
To fix this issue, please update the docker-compose.override.yml file during builds.
Row 35 should read: image: jrcs/letsencrypt-nginx-proxy-companion:latest
This will insure that the current version for the let's encrypt proxy is called and eliminate the issue.
-
@krzykat said in Postcards for SMS by Skyetel.:
Row 35 should read: image: jrcs/letsencrypt-nginx-proxy-companion:latest
Well, they listened to you. Line 35 is just as you say it should be.
-
Have you checked your LE credentials to see that its working properly?
-
@krzykat said in Postcards for SMS by Skyetel.:
Have you checked your LE credentials to see that its working properly?
Not sure how. The only sign of LE I can find in the OS or the Docker is a file called letsencrypt_services_data
I can't find a conf file or a binary to do a manual run of LE.
