• 3 Posts
Joined 2Y ago
Cake day: Nov 12, 2021

I have a, fairly, new instance up with several people examining the moderation tools. Someone noticed that the 'remove' option at both the post level and the comment level could be improved upon and I agree with them. Our conclusion is that these would be more user-friendly/intuitive if they were 'remove post' and 'remove comment' respectively.

I can’t believe that I missed that! Thank you.

How do I upgrade to latest Lemmy UI?
Using Docker, I've upgraded Lemmy from 0.13.0 to 0.14.1. How do I upgrade to the latest Lemmy UI?

I think I may have found something. Instead of using ‘restart’ with nginx shouldn’t I be using ‘reload’? See: https://linuxize.com/post/start-stop-restart-nginx/

reload: Gracefully restarts the Nginx service. On reload, the main Nginx process shuts down the child processes, loads the new configuration, and starts new child processes.

I’ve never used docker-compose restart. I always use docker-compose up.

Did you previously have www.beehaw.org set in docker-compose.yml? Maybe its still using the old setting.

I may have. I don’t know how it could retain the old setting. Strange. Thanks for helping.

Here are the server blocks of my nginx conf file:

server {
	if ($host = beehaw.org) {
		return 301 https://beehaw.org$request_uri;
	} # managed by Certbot
	listen 80;
	listen [::]:80;
	server_name beehaw.org www.beehaw.org;
	location /.well-known/acme-challenge/ {
		root /var/www/certbot;
	location / {
		return 301 https://$host$request_uri;


server  {
	listen 443 ssl http2;
	listen [::]:443 ssl http2;
	server_name beehaw.org www.beehaw.org;
	ssl_certificate /etc/letsencrypt/live/beehaw.org-0001/fullchain.pem; #managed by Certbot
	ssl_certificate_key /etc/letsencrypt/live/beehaw.org-0001/privkey.pem; #managed by Certbot

OK. Thanks for taking the time to try and resolve this. I appreciate it.

Can you link your instance…

If you mean federate, then we aren’t comfortable doing that.

I installed using these instructions: https://join-lemmy.org/docs/en/administration/install_docker.html

# address where pictrs is available
  pictrs_url: "http://pictrs:8080"

Bad certificate warning
My site certificate **only** supports non-www addresses. So, when we try to access an image uploaded to the site we are getting a bad certificate warning because there is a 'www' in the address. Is there a solution for this?