-
[Support] Linuxserver.io - Bookstack
Well after countless hours of trying to get this docker started I finally managed to reach the login screen. Thanks to the pointers about the issue with special characters in the password. Mine did not have a # but had a few other special characters: }[24+KsM;7=)AVe24zHR64U2NtLG/RH It would not generate any error and I would just get a blank screen after launching the docker. The database would stay empty too. Changing my password from the above to one without special characters did the trick! Just in case this helps anyone else
-
Recommendation for 1GB NIC Network card (4 ports)
OK after some further research and based on the info from the FreeBSD site, I ordered an Intel Quad Port Ethernet PCIe card (0HM9JY). It is supposed to support all PfSense features... Just posted this it case it might help someone else along the road
-
-
Recommendation for 1GB NIC Network card (4 ports)
Greetings, I am currently using the built-in network ports of my motherboard for my UnRAID server. All fine and good. I would like to install PfSense in a VM and for that I would like to purchase an additional NIC card, preferably with 4 ports. I watched SpaceInvader's pfSense series, were he recommends using NICs with original INTEL chips. Are there, more generally speaking, any specific models that are known to work really well with UnRAID? Any specific recommendations would be very helpful 😀
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
Hi again One more clarification please Below is the content of the root file in the crontab folder: ------------------------------------ # do daily/weekly/monthly maintenance # min hour day month weekday command */15 * * * * run-parts /etc/periodic/15min 0 * * * * run-parts /etc/periodic/hourly 0 2 * * * run-parts /etc/periodic/daily 0 3 * * 6 run-parts /etc/periodic/weekly 0 5 1 * * run-parts /etc/periodic/monthly # renew letsencrypt certs 8 2 * * * /app/le-renew.sh >> /config/log/letsencrypt/letsencrypt.log 2>&1 ------------------------------------ Am I reading this correctly, if I interpret that as below? Monthly maintenance is run every FIRST day of the month at 5.00 AM AND Weekly maintenance is run every SATURDAY at 3.00 AM AND Daily maintenance is run every DAY at 2.00 AM AND Certificate renewal is run every DAY at 2.08 AM? 1) Not sure how to read the 15 mins and hourly lines... but that's really for my own curiosity 2) Since there is a daily maintenance already, what would be the point in having the weekly and monthly active too? 3) Is the daily renewal done at 2.08 AM in order not to conflict with the 2.00AM maintenance? 4) Finally, if I want to set the renewal to 7PM, I guess I just replace the '2' with '19'? Thanks again
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
Perfect! Many thanks thanks for your reply! [emoji3]
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
Greetings I have a couple of questions regarding the (automated?) certificate renewal of the LetsEncrypt container: I have recently set up my first reverse proxy following Ed's tutorial and everything seems to be working fine. Since I am not yet actively running any apps behind the reverse proxy, I have stopped the LetsEncrypt container and closed the relevant ports on my firewall. However, I now have received my first email notification saying my certs will expire in the coming 2 weeks. My understanding is, and please correct me if I am wrong, that while the container is actively running, there is a Cron job running every night at 2 AM to auto-renew the certs? 1) Is that a fully automated renewal where I don't need to do anything? Or do I need to push any commands manually? 2) Is that a daily or a weekly check? I seem to have read contradicting statements about this. 3) Is it possible for me to modify that 2AM hour and set my own time of the day? Since I am not actively running the container for now I'd rather not wait until 2AM to try it out. Yes I know I can just leave it running and check the next day, but I am still very cautious about having ports 80 and 443 open to the Internet. For now I would prefer just to open the ports on a per need basis when I renew the certs. Many thanks in advance for any clarifications and guidance
-
Trying to add a remote SMB share (Synology)
Yes I managed to get it to work. The issue seemed to be on the Synology side somehow with my existing user. I suspect some conflict with mounting the shares both from my computer and UnRAID at the same time. I ended up creating a new user on the Synology that I dedicate to accessing the media library. - Create a new user - Make sure he has the right permissions to READ the share on which your media library is stored (e.g. MEDIA) - In UnRAID, add //DISKSTATION/MEDIA with those credentials (use the name of your Synology or its IP address) Hope that will work for you too Cheers
-
Trying to add a remote SMB share (Synology)
Version: 6.7.2 + Unassigned Devices plug-in Greetings :) I have set up the PlexPass Docker container and am now trying to make my media, which is hosted on a separate Synology NAS, visible to my Plex docker as my media is not yet stored on my array. Using the Unassigned Devices plug-in, I am attempting to add a remote SMB share but no luck so far: In the UD plugin, I put in the IP of my Synology and search for servers. It properly locates my server under its host name. I select that and enter both a username and password for an account that I know has the proper access rights for the share. When pressing the 'Load Shares' button, I get a quick loading animation but no shares are listed to be selected. I tried adding the share manually in different ways, but I can't get that to work either. I tried things such as: /volume1/media/ /volume1/media /volume1/ /volume1 All allow me to add the remote share but the subsequent mounting does not work. What am I missing here? The share mounts with no issues on other devices. The Synology is also configured to allow for SMB1-3 protocols, so UnRAID will try SMB3 first then the others if I am not mistaken. Any thoughts?