fizzle

I don’t know the actual reason, but I personally get a bad vibe every time I see the logo because usually it means I’m trying to install or fix some java bullshit, which never goes well.

I didn’t know this was ever in question?

Also stop calling it “my sequel”

All the obvious things have been mentioned.

The only way to identify the problem is to share the exact steps youve followed and then others can reproduce.

Based on what youve told us, no one knows how the subdomain is leaked. Without meaning to be derisive, that suggests that something youve told us isn’t quite correct.

I dont think this really responds to the comment you replied to.

Lots of comments in this thread are talking about people who dont have the time or expertise to manage their own nextcloud instance.

Saving you stuff on your neighbour’s instance includes genuine risks to your privacy or sensitive information.

The “legal agreements” that commenter referred to are simply the manner in which the host is allowed to use your data. The things you might store might be your will, maybe a spreadsheet of passwords, maybe some notes about your plans for a side hustle, maybe some naughty photos of your wife. Not information thats actionable by Google or Microsoft, but certainly things people dont want their neighbour to access.

There’s an open issue about this on github. It’s the remote API is only recognising the first word of your query.

This has been bugging me too.

The timeouts are because the engines are presenting captchas. There’s a work around whereby you use your instance as a proxy, navigate to that remote engine, and do the captcha.

These two issues are a real pain in the ass so while I do presently have a searxng instance I’ve been using qwant the last few weeks because I’m just over it.

Never used containers on synology.

Seems weird to me that there’s an AIO container that seems to contain other containers, but anyway I guess thats a synology thing.

Maybe this is obvious to everyone else but… all those containers are “starting” because theyre waiting for one other container to finish “starting” before starting up themselves.

I agree that the redis warnings seem benign.

Weird that nextcloud is waiting for a db but postures says its ready.

Is the 404 in the master container logs from you trying to access the instance in your browser?

I assume there’s some kind of compose.yaml as part of the AIO project you’re installing which will reveal which containers “depends_on” which other containers so you could figure out which one is blocking you.

Containers have layers. So if you create an instance of a syncthing container whoever built that container would have started with some other container. Alpine linux is a very popular base layer, just used as an example in this discussion.

When you download an image, all the layers underlying the application that you actually wanted, will only be as fresh as the last time the maintainer built that image. So if there were a bug in the alpine base, that might have been fixed in alpine, but wouldn’t by pushed through to whatever you downloaded.

I’m also in this category, but OP is talking about something else.

Like if you use container-x, which has an alpine base. If it hasn’t released a new version in several years then you’re using a several year old alpine distro.

I didn’t really realise this was a thing.