walden

I have multiple things running through a reverse proxy and I've never had trouble accessing them until now. The two hospitals are part of the same company, so their network setup is probably identical.

Curiously, it's not that the sites can't be found, but instead my browser complains that it's not secure.

So I don't think it's a DNS problem, but I wonder what the hospital is doing to the data.

All I could come up with in my research is this article about various methods of intercepting traffic. https://blog.cloudflare.com/performing-preventing-ssl-stripping-a-plain-english-primer/

Since my domain name is one that requires https (.app), the browser doesn't allow me to bypass the warning.

Is this just some sort of super strict security rules at the hospital? I doubt they're doing anything malicious, but it makes me wonder.

Thanks!

Also, if you know of any good networking Lemmy communities, feel free to share them.

I don't really know what to look for in the logs, but with some guidance maybe we can figure this out. Here's how it typically goes:

Set up daily recurring auto-post at sub.wetshaving.social. It works for about 1-2 weeks, then stops.

I set the entire server to restart every 3 or 4 days, which makes Lemmy Schedule stable for longer, but still every week or two it will stop working.

The solution is some sort of combination of restarting the Docker stack (Lemmy Schedule and Redis) and/or opening the Lemmy Schedule web interface and logging in, logging out, refreshing, logging back in, whatever it takes. The need to load the web page is odd, like it reminds Lemmy Schedule somehow that "oh yeah, there are posts to post".

A lot of times when I log in to fix it, the scheduled post does not appear in the to-do list. We have a weekly post that stays in the to-do list, but not until I reload, log out, etc. will the daily post eventually find itself and reappear in the list.

When it starts working again, it typically spits out the posts that it missed, sometimes in duplicate.

Any ideas?

I've seen them called "Stop Lines", "Balk Line", etc. The thick line painted on the road at a Stop Sign.

You're supposed to stop before the line, but a lot of the time there's a bush or other obstruction so you can't see any crossing traffic. You have to creep forward until you can see anything.

Is there a reason for this? Is it done on purpose? It makes sense if there's a crosswalk or something, but I see it a lot where there shouldn't be any pedestrian activity.

I've found the following work-around works pretty well. If you host an instance that's currently on 0.19.0 or 0.19.1, consider implementing this.

There are two bugs that this helps with:

• Outgoing federation stops after about 6 hours
• Another federation bug which is triggered if the server isn't running at midnight every night

Work-around:
Create cronjobs that restart the Lemmy container every 6 hours (but not at midnight). The following example is used for a Debian system running Lemmy in Docker.

Type crontab -e into the terminal Add something like the following:

~~0 1 * * * docker container restart lemmy-lemmy-1
0 7 * * * docker container restart lemmy-lemmy-1
0 13 * * * docker container restart lemmy-lemmy-1
0 19 * * * docker container restart lemmy-lemmy-1~~

3 1-23/6 * * * docker container restart lemmy-postgres-1 && sleep 60 && docker container restart lemmy-lemmy-1

By restarting the container every 6 hours, outbound federation continues to work. There may still be some delays, but everything gets cleared up regularly.

By telling it what time to restart (0100, 0700, 1300, and 1900 as opposed to "every 6 hours"), it avoids restarting at midnight. This avoids the second bug.

My instance has been doing this for enough days where I'm confident that it's working. You can check your federation status here. Note that it's normal for there to be 0 up-to-date instances and a lot of lagging instances. As long as they sometimes turn "up to date", then everything is getting caught up.

We have a small but dedicated user base. The community has daily posts to share your shave of the day (SOTD) so you can easily see what other people have been using. Other posts are allowed, like mail calls, reviews, or any other interesting shave content.

Yes, we really enjoy shaving that much!

!wetshaving@sub.wetshaving.social