-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nginx 503 Error #4
Comments
Can you post the output of:
? |
Sure, I got the logs! Sorry for the delay. Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.40/containers/pleroma/json: dial unix /var/run/docker.sock: connect: permission denied |
|
ok. i just installed on the pi 3b+ and got this error. interestingly, if i access the device local ip address http://192.168.29.242/, it says
if i access the actual subdomain i have used, it says pleroma with blank page but source says
then if i access, https://www.pleroma.local/ or http://www.pleroma.local/, it says problem loading page. here are logs from sudo docker logs pleroma | nc termbin.com 9999 after a reboot, some of these urls are showing
|
same for http://pleromapi.local/
|
Just to confirm my domains, |
The reverse proxy redirects based on the host url. So pleroma will only work for the host domain you set in:
|
i checked dockercompose/02_pleroma/environments/pleroma correctly to my url. |
Can you share it?
…On Thu, May 20, 2021, 12:33 test2a ***@***.***> wrote:
i checked dockercompose/02_pleroma/environments/pleroma correctly to my
url.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACPQJTOQPMIYA3M5MHJJT3TOTJPBANCNFSM433RUURQ>
.
|
yep. wait a min |
i have replaced the actual domain name and email. otherwise its fine. anyway to check from terminal these figures? |
Ok, and when you put the equivalent of |
i get the blank page and it contains the source i have linked above.
this one. |
are you online on mastodon ? i can send you the actual url so you can see for yourself |
@guysoft hi. i found out others have had this same issue. https://git.pleroma.social/pleroma/pleroma/-/issues/1238 |
Yes I am at @[email protected] and @[email protected] That issue is over a year ago before PleromaPi existed, so not sure how it relates. Its strange, it looks like Pleroma is loading, but something is set up wrong. |
Ok, I managed to reproduce and fix the issue. This is the commit that fixes it: The issue is that the lets encrypt container that the image uses was broken. I updated it to use a good one. As you can see in the commit. The reason you get a white page is because Pleroma does not serve on http, and with LE not working its using http and not https. You can update the image as shown in the commit, or you can wait and I will release a new image. |
I'm a little baffled by this.
Pi: 4, 4GB
MicroSD: Sandisk Ultra 128GB
I've tried both stable and nightly images.
So, I follow the instructions, I burn the image, I setup the WPA supplicant file, I setup the environment variables, and then I wait for a little while before trying to connect to pleromapi.local.
The good thing is is that pleromapi.local is accessible, and I can SSH into the Pi, but the problem is is that it isn't serving up the page. Instead I get a 503 error.
I'm not sure what I'm doing wrong.
The text was updated successfully, but these errors were encountered: