Since update css broken?

[timbo]

Can confirm the CSS is just not receivable.
Also found, that it might have to do with the issue i posted about yesterday, which is already fixed by @girish, where the

  domain: process.env.CLOUDRON_APP_DOMAIN

was wrong.
Since i updated the App with this fix, CSS does not work because Firefox receives HTTP 404 Error when GET the CSS files.

[LoudLemur]

I was ugly too:

There is an option to export preferences in a json file in preferences. You can import it later.
I tried the reinstall Teddit trick and ... the problem remains. On the plus side, it looks like Cloudron kept all the configurations I had made too (e.g. subscribed sub-Reddits).

The problem looks the same in Brave beta and in TOR-browser.

By the way, before this happened, I noticed that increasing the memory allocation to Teddit helped with playability of some of the video content posted.

[timbo]

@LoudLemur said in Since update css broken?:

it looks like Cloudron kept all the configurations I had made too (e.g. subscribed sub-Reddits).

Cloudron actually does save nothing.
Teddit is per design privacy focused on a maximum.
Nothing you do while using Teddit is stored or saved server side. It all happens client side in your browser using cookies etc.
Only what you configure in the config.js is being saved server side.

[girish]

@timbo said in Since update css broken?:

domain: process.env.CLOUDRON_APP_DOMAIN

Note that this fix has to be applied manually on existing installations. I didn't bother fixing the upgrade code path because the app was still marked as unstable. Sorry about that!

[timbo]

@girish Yes i already fixed it manually but there also was an update available to the app, bringing it to 0.4.0 which has the correct

domain: process.env.CLOUDRON_APP_DOMAIN

( 21:53 App was updated to v0.4.0
21:52 Update started from v0.3.0 to v0.4.0)

as in https://git.cloudron.io/cloudron/teddit-app/-/commit/530c2febb9a3f30ebe28ecf939e4c5950299937c

[girish]

@timbo right. I was actually writing that comment for @necrevistonnezr and others

[randyjc]

@robi was looking exactly for this info. Thank you

[timbo]

dont know if this has to do something with the css failure, but when starting the app this error will be logged:
localstorage undefined
proxyAuth undefined
redis undefined

[nebulon]

Those undefined logs were accidental debugging logs left in the code in the previous release, those are not relevant.

[timbo]

Ok so i am a little confused.
After reinstalling the whole app, i expected to run into the same issues as:

@necrevistonnezr said in Since update css broken?:

After clicking on any thread, the css for that thread is broken

List of threads:

Thread:

but for whatever reason, i did not.
First the network-analysis in firefox showed that the missing files to the stylesheets, which previously got 404ed, were cached instead of being served by the webserver.
After clearing the cache it actually did receive (200) the stylesheets from the webserver.

So everything works for me, across devices, across different privacy settings.

[LoudLemur]

I still have the problem. I can't see how to clear any cache for this particular site. After visiting the teddit, F12,

[timbo]

Can't help you with your exact setup, but in firefox on mac i can reload the page bypassing cache using cmd+shift+ r

[girish]

It might be easier to just reinstall. Doesn't reinstalling help?

[Meuschke]

@girish for me, it didn't.

But after reinstall, everything shows up correctly, if I change the data directory, or maybe after reboot, the problem stays. I don't know what it causes.

[girish]

@Meuschke can you set up an instance on the demo cloudron and see if you can reproduce it there?
https://my.demo.cloudron.io/ (username and password is cloudron) . I tried everything and haven't been able to reproduce yet.

[Meuschke]

@girish it works on the demo-instance. Could you please create a volume on /srv/apps/teddit for example and link the teddit files with it [on App ==> Storage]?

Do you want to take a look on my server maybe?

[LoudLemur]

I just tried the re-install on a different sub-domain trick. It didn't work for me. It looked just the same.

[girish]

@Meuschke I moved it a volume on the demo and ... broken. Investigating.

[Meuschke]

Thank you @girish !

[girish]

@Meuschke can you update and try?