Empty white page after installing and trying twice

[nebulon]

Actually that domain shows a mastodon instance. Maybe your DNS cache is not updated?

[masto77]

@nebulon

I purged the cloudflare cache too and tried clearing my browser cache it’s the same yet I’m attaching a screenshot.

[masto77]

@nebulon

After trying multiple times it worked on incognito mode I did clear the browser history too why isn’t it working in a normal tab.

[nebulon]

@masto77 this is hard to say and likely specific too your browser environment. Do you have any security/privacy addons installed which might cause this?

[girish]

I suspect this is the same as https://forum.cloudron.io/topic/8014/mastodon-behind-cloudflare . IIRC, there are two things:

• Check the TLS proxying mode in Cloudflare. This needs to be Strict and use full https proxying for Cloudron. By default, it was insecure and using http.

• Check the browser console for CSP errors. Cloudflare was injecting some analytics javascript which mastodon's CSP prevents and this makes mastodon not load.

[masto77]

ok am going through this as well @nebulon

using mastodon official iOS mobile app I’m not able to attach any image it gives this

But it works on web interface however I’m not able to attach any image regardless of its size whether it’s small or large using mastodon iOS app

[masto77]

@nebulon

No I don’t use any addons just cloud flare basic no extra on it

[girish]

Reading this again, it's not clear to me: is Cloudflare proxying enabled or not? If you have it enabled, have you tried without Cloudflare proxying?

[nebulon]

Is it possible that your server runs out of memory? Or the mastodon app crashes out of memory?

[masto77]

@girish

Thanks it’s already working I got your point cause with proxying ttl is auto.

I wasn’t trying it without proxy.

but hanged with not being able to image posts using official mastodon iOS app

The web works

@nebulon

No such reports I have extended memory up to 3GB and the server has 4GB

[nebulon]

Maybe there is some language barrier, but it might help to give more detailed background information so we can help you.

I assume the 502 error is now something different to your initial issue. Do you see any errors in the app logs or browser console or something?

[masto77]

@nebulon

I just googled this issue I’m not sure if it is specific to uploading image through iOS mastodon app

These google references I found says nginx buffer needs to be increased I have no idea how to do it while at cloudron

This happens only on official mastodon app to me, I tried using metatext app it works fine

[nebulon]

This further indicates that something is rather on the client side or how that specific client of yours interacts with the server. Do you see any errors in the server side app logs which might give any indication? Without more detailed information from your side, this is mostly guesswork on our end.

[masto77]

This post is deleted!

[masto77]

@nebulon

I found this from google no idea how to do it?
and this is marked as a solution

https://discourse.joinmastodon.org/t/502-bad-gateway-connection-refused-while-connecting-to-upstream/3396

“”
It seems you forgot to run the bundle exec rails assets:precompile step or it failed.””

[nebulon]

@masto77 actually we do run that step in the image building https://git.cloudron.io/cloudron/mastodon-app/-/blob/master/Dockerfile#L44

We also have a lot of mastodon installations amongst our users who don't seem to face that issue, which makes me even more think, that this is something related to your specific mastodon client.

I do not have any iOS devices to test this with, but maybe other can comment if they face the same or a similar issue?

Have you looked at the server side app logs yet? You can find the logviewer as described at https://docs.cloudron.io/apps/#log-viewer

[masto77]

@nebulon

Thanks!

I found this too may be it’s related which states to increase the buffer I have no idea where to find this or how to do it ?

“
A possible fix for this is to modify the nginx conf to increase the proxy buffer. The following worked for me:

proxy_buffers 4 16k;
proxy_buffer_size 16k;
proxy_busy_buffers_size 32k;

“