-
-
Notifications
You must be signed in to change notification settings - Fork 628
[Maybe Solved] Cannot run on ARM Ubuntu #347
Replies: 1 comment · 3 replies
-
I haven't tried in ARM but if ningx-proxy and you got that far running the three containers, it should work as well. We would need some logs to check that is really the case, but did you update the nginx template when running the fresh-install.sh without options? I would start from there, make sure ports are not being used and old settings were not in place. Send the full set of logs from nginx-proxy container. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Yes, this is a ARM server with a newly docker installation. Your repo was the first thing on docker. I did a full delete of the entire proxy folder after each trial, so there are no artifacts from previous settings. When looking around, people point to either Here are the logs on a just new git clone + setup following instructions on ReadMe page.
Logs (long!)
|
Beta Was this translation helpful? Give feedback.
All reactions
-
It seems your nginx conf file is missing... do you have ipv6 running in this server? might disable the ipv6 in nginx proxy and try again and make sure to update the conf file for the nginx proxy. your log says:
run the fresh-install with '--update-nginx-template' flag as well so you update the nginx template from nginx-proxy. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Hello, it does not have IPv6. I ran the command you gave, and it worked. I am not sure whether the command fixed it, or whether I had fixed it via some other ways (I had it running via the original proxy method) unknowingly. I checked the logs and did not get that error anymore. Unfortunately, I do not have another ARM instance I can provision as of right now to test on a new machine. I will leave this Thread here for now in case others stumble upon it or if I can find another ARM instance. |
Beta Was this translation helpful? Give feedback.
All reactions
-
🎉 1
-
Hello, I followed the instructions to set up this repo, and I noticed that it does not work for me on a ARM Ubuntu. I have deployed this tool very easily (thank you very much for this tool again) on some VPS which were AMD-based, so I think I did not make a mistake setting it up on the ARM machine.
I tried both the quick way of
./fresh-start.sh --yes -e your_email@domain --skip-docker-image-check
as well as trying./fresh-start.sh
manually. I also tried to checkout to earlier git commit that I know worked on my AMD VPS.The below is the error I see most often when running
docker-compose logs
The reason I was able to pin it down to being ARM and not firewall, iptables, etc was because I was also unable to deploy some other docker images unless they explicitly supported ARM. After some digging, the official
nginx-proxy
does support ARM. Therefore, I created a docker-compose from the link below (choose three containers), and it worked.https://github.com/nginx-proxy/acme-companion/blob/main/docs/Docker-Compose.md
Beta Was this translation helpful? Give feedback.
All reactions