What version do you have? I think you have one of the older versions, you can find the latest one here: https://github.com/dessalines/jerboa/releases/tag/0.0.26
Try removing the lemmy.conf file from /etc/nginx/sites-enabled,
And then run:
sudo wget https://raw.githubusercontent.com/Kradyz/Tutorials/main/files/uebishe.conf /etc/nginx/sites-enabled/uebishe.conf
sudo systemctl restart nginx
Or, I have made an nginx config file that will work for you
If you already created an nginx configuration file, move it somewhere else. Then, get the new configuration file to the nginx folder, and then restart the nginx service by running these two commands:
sudo wget https://raw.githubusercontent.com/Kradyz/Tutorials/main/files/uebishe.conf /etc/nginx/sites-enabled/uebishe.conf
sudo systemctl restart nginx
Ah! So you skipped this step:
Now i skip old step about “wget https://raw.githubusercontent.com/LemmyNet/lemmy-ansible/main/templates/nginx.conf -O lemmy.conf”
You need to have the lemm.conf file under /etc/nginx/sites-enabled, this is the file that tells nginx how to manage the connection. Don’t skip that step! Get that file and modify it by adding your domain name
Sorry, I did not realize that these files had not yet been updated with the changes necessary for version 0.17.0, which are described here: https://github.com/LemmyNet/lemmy/blob/main/RELEASES.md#lemmy-v0170-release-2023-01-31
I could not find an example of the files configured correctly in github, so I have uploaded some example files. You get them this way:
wget https://raw.githubusercontent.com/Kradyz/Tutorials/main/files/lemmy.hjson
wget https://raw.githubusercontent.com/Kradyz/Tutorials/main/files/docker-compose.yml
Then modify the variables inside {}, like the domain name and the database password.
Remove the following blocks from the docker-compose file:
networks:
# communication to web and clients
lemmyexternalproxy:
# communication between lemmy services
lemmyinternal:
driver: bridge
internal: true
proxy:
image: nginx:1-alpine
networks:
- lemmyinternal
- lemmyexternalproxy
ports:
# only ports facing any connection from outside
- 80:80
- 443:443
volumes:
- ./nginx.conf:/etc/nginx/nginx.conf:ro
# setup your certbot and letsencrypt config
- ./certbot:/var/www/certbot
- ./letsencrypt:/etc/letsencrypt/live
restart: always
depends_on:
- pictrs
- lemmy-ui
And try again. Does it work?
Do you want to install a fresh instance, or do you want to upgrade an instance?
If you are installing fresh, most of that tutorial is still going to work out. But you now need to pull the config file this way:
wget https://raw.githubusercontent.com/LemmyNet/lemmy/main/config/defaults.hjson lemmy.hjson
If you install the more recent docker version, you don’t have to install docker-compose the same way. Follow the instructions from the website, and use ‘docker compose’ instead of ‘docker-compose’.
The nginx configuration does not need to change.
What problems are you getting?
No problem!
I thought it was a UI issue so I had created an issue there: https://github.com/LemmyNet/lemmy-ui/issues/918
There is a newer version that fixes this: https://lemmy.ml/post/743037
An issue was opened for that three days ago:
https://github.com/LemmyNet/lemmy/issues/2678
I don’t think it is possible through the UI at the moment.
Also, did you change the variables in the Lemmy UI environment?
(Edit to specify, in the docker-compose.yml file the variables are now different)
The lemmy-ui environment variables have changed, and should now look like:
environment:
- LEMMY_UI_LEMMY_INTERNAL_HOST=lemmy:8536
- LEMMY_UI_LEMMY_EXTERNAL_HOST={{ domain }}
- LEMMY_UI_HTTPS=true
There are also other instructions that you need to follow. Are you following the release note instructions?
See: https://github.com/LemmyNet/lemmy/blob/main/RELEASES.md#lemmy-v0170-release-2023-01-31
I just checked, and it is still possible to determine who has liked/disliked a specific comment or post in 0.17 by running a database query.
It is not something that I personally have a problem with - I suspect this might be a “necessary evil” to prevent double voting. And I would think that this is the default for any site with voting.
Hey, I had missed this post when I replied: https://feddit.de/post/541248
This site helps you search for communities in many instances at the same time: https://browse.feddit.de/
Might be helpful too!
You mean that you want to stay within lemmy.ml, connected to your user, and replace the content with the content from heapoverflow.ml? Then you would be able to explore instances more easily and find new communities to subscribe to.
There is no way to do that at the moment. Lemmy.ml only fetches some of the content from other instances - such as the content that lemmy.ml’s users are subscrribed to, and the content that is manually requested by pasting the original Url into the searchbox.
I can’t think of an obvious way that this can be implemented without fetching a large amount of unsued content from the other instance, and that approach would become very resource inefficient as instances become larger.
Another approach could be to create instance relays or explorers that are modified instances that will focus their resources on discovery by fetching a lot of content that might live for a week or two in the instance, and then build tools into it such as filtering by instance. This instance would subscribe to every community of the instances in its list. You would still need to leave your instance’s site to explore instances, unless the relay is somehow connected to the original instance, but at least this would be an efficient way to explore.
As of now, what I do is that I manually explore instances by accessing their site in a new tab, and manually subscribe to new communities by copying and pasting the community Url into mine.
Yes, that is how I did it :-)
It works for communities because their relative url is always /c/community@instance.tld
For posts and comments it won’t work because the post and comments IDs are different for each instance. For example, this post is at https://mander.xyz/post/520556 at mander and at https://lemmy.blahaj.zone/post/6506 at blahaj.zone, so the relative urls are different.
- •
- 4M
- •
- •
- 4M
- •
True! And with shrooms it is exciting to see how they change so dramatically in days.
It took me months to get my yagé (Banisteriopsis caapi) seeds to germinate, and it takes weeks to grow new leaves and drops the previous ones. I really hope I manage to keep it alive! So every leaf is a pretty welcome surprise.
My chacruna (Psychotria viridis) seeds won’t germinate after over half a year of trying 😓
- •
- 4M
- •
- •
- 4M
- •
- •
- 4M
- •
I agree. This can easily be exploited by a malicious mod. Since the original poster can still edit the title, it is better to just ask them.
Remember when Reddit’s CEO /u/spez decided to abuse his super-powers to edit user comments? That was not very well-received by the community.
The majority of new accounts created at mander.xyz would post ads about pills or crypto wallet scams shortly after being created. Now I have to manually accept registrations, and many do write that they want to make a post about their product. I deny those. But a few do get through.
I am not sure that they are bots, though, because they do fill in the registration form. And I might be wrong, but I think that a bot would need to be tuned specifically to interact with lemmy instances. I think that these might be actual people that manually crawl the web and spam.
- •
- 1Y
- •
The MAX_TITLE_LENGTH is applied to posts that are fetched from other instances using activitypub. The posts that are posted within an instance do not pass through that processing step.