I had a similar issue on an HP Elitedesk 800 mini G3. It turned out to be a faulty ram stick. Memtest revealed the issue and after unpligging the defective stick the issue was resolved.
Hi, thanks. I’ve been testing out NextCloud and it might be a bit too bloated and buggy for me (document editor iffy on mobile and encountering files and folders being falsely locked and thus cannot be interacted with) so I might give sftp a go.
Is there a dockerhub project you would reccomend? I’ve been looking at sftpgo (https://hub.docker.com/r/drakkan/sftpgo) as a option?
To prevent brute force login attempts into my jellyfin service.
Oh I can see how my title could be misunderstood - what I meant is that both jellyfin and fail2ban are running in (separate) docker containers. Not both services crammed.into one.
Thank you. I did see this list before. My jellyfin instance is not exposed to the net atm., but I’m thinking of exposing it in intervals and would like to have fail2ban working when/if I do.
Hi,
I’ve been trying to set up fail2ban for jellyfin both running in docker from compose and I’m doing something wrong.
Can someone tell me what path in the docker compose file you use for jellyfin logs and what path you use in the jail.d and the filter in filter.d?
Thanks
PS. Sorry for low detail, but I’m on phone and don’t have my current conf readily available. Will provide if necessary.
Hi,
I’ve been following this guide to set up some basic selfhosted services (video) https://www.youtube.com/watch?v=qlcVx-k-02E (text) https://notthebe.ee/blog/easy-ssl-in-homelab-dns01/
I’ve managed to get things working, but DuckDNS (duckdns.org) seems to be unresponsive most of the time. I then tried to register my DNS at FreeDNS (freedns.afraid.org), but the generation of a ssl certificate in Nginx fails. I get the following error message in Nginx:
CommandError: Saving debug log to /tmp/letsencrypt-
log/letsencrypt.log
Some challenges have failed.
Ask for help or search for solutions at
https://community.letsencrypt.org/. See the logfile /tmp/letsencrypt-
log/letsencrypt.log or re-run Certbot with -v for more details.
at /app/lib/utils.js:16:13
at ChildProcess.exithandler (node:child_process:430:5)
at ChildProcess.emit (node:events:518:28)
at maybeClose (node:internal/child_process:1104:16)
at ChildProcess._handle.onexit (node:internal/child_process:304:5)
The domain I chose is <my_subdomain>.privatedns.org.
Does anyone know how I can get Nginx to succeed in generating the ssl certificate so I don’t have to start deploying ssl generation myself?
If I have to do it myself any useful resources will be appreciated.
Thanks :)
I did the same. Not because I knew, but because I was unsure if permissions would fail if I didn’t.
Do I just enter the container shell and check GID and UID of a random file?
I’m CURSED I tells ya! I’ll look at the logs tomorrow. Good to know that you can get it working. Maybe I’m close then.
Do I need to enter the container bash and change something then? I tried adding UID and GID to the docker compose file, but it still fails. I updated the google docs notes if you want to see my steps.
Thanks for the suggestion. I tried and it still doesn’t work. I updated the google docs notes with my steps if you want to see what I did.
How do I tell? In the docker-compose.yml file I put the user and password for my server user. I thought that was going to make it work?
Hi, I made this post a few days ago: https://lemmy.world/post/27391713 And I’ve been trying a lot of stuff and it doesn’t work and it’s driving me nuts. Now I tried again from the bottom and wrote down everything. You can see my notes here: https://docs.google.com/document/d/1vPplJhjZ13j1A2mEzHGS1B_sPSThE3LHxnGW82_F6Is/edit?usp=sharing Can anyone tell me why I keep banging my head against a wall here? Thanks :)
Update: It worked all along. All I needed to do was restart my windows machine and the errors would go away and I could enter the share. Good times.
I did fiddle with it. I tried putting my server user and password in there, but didn’t get it working.
Well, I’m not trying to share from within the docker container. I just want to run the samba service from a container. The share is an external hard drive connected to the server. I want to be able to move files to and from the ext hdd from a windows machine.
Hi, I’ve tried running samba from docker compose on ubuntu server with this resource https://hub.docker.com/r/dockurr/samba I changed the default volume from “- ./samba:/storage” to “- /mnt/my_ext_hdd/my_dir/my_subdir” The container deploys fine, but I get permission error when trying to access the shared volume from windows? Anyone with some suggestionshoew to fix? Thanks
I would prefer that it’s only accessible for users I approve through some sort of whitelist. That would be friends and family.
Hi, I got a small server as a for-fun-project and I really enjoy having it. With all the stuff going on in the world I would like to self host more things, but I’m pretty new to the scene. So far it’s just an old desktop with Ubuntu server os acting as media server. I would like to add some sort of lightweight and preferably open source file share akin to Google Drive with the ability to save/upload, view and edit files on the server from the outside internet. I’d also like a shared calendar that can also be accessed from the internet. Do you have any good recommendations this? Thanks
Thank you for your thorough analysis and report. Very interesting read. Just doing the basics, as you say, is more than a layman like me can do!