Everything posted by WannabeMKII
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
OK, so I've change port forwarding to 80, 80 and the internal IP. I've changed HTTPVAL to 'true' from 'True'. On running the docker, I get the following in the logs; Performing the following challenges: Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA. Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA. ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container Any other ideas?
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
I'm running Radarr, so opened the port for the container on my router to the IP the docker is running and entered the IP followed by the Radarr port and it opened without a problem. Is that what you mean? I'm just trying to help out, as this is really strange and really frustrating, so keen to help find the resolution.
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
How would I do that?
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
I wonder if something has gone wrong between the backup and restore?
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
OK, so I've opened another port as an experiment and it's worked perfectly. Would LetsEncrypt not respond or report the ports as closed?
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
My ISP, BT, don't block port 80, as I've used it in the past. Infact, I was using up until I updated unraid to 6.4. I'm really confused why port 80 is showing as closed though when the port is open on the router and BT don't block it? Strange, it's also reporting 443 as closed and I was also using that yesterday up until the update in unraid?
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
Sorry, paranoid I guess. Here's the run command; root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="letsencrypt" --net="br0" --ip="10.0.0.220" --privileged="true" -e TZ="Europe/London" -e HOST_OS="unRAID" -e "TCP_PORT_80"="81" -e "TCP_PORT_443"="443" -e "EMAIL"="*****@*****.***" -e "URL"="*****.*****" -e "SUBDOMAINS"="*****" -e "ONLY_SUBDOMAINS"="true" -e "DHLEVEL"="2048" -e "HTTPVAL"="True" -e "PUID"="99" -e "PGID"="100" -v "/mnt/user/appdata/letsencrypt":"/config":rw linuxserver/letsencrypt fe5d2e9caaf15a0373feb2834d6b278c4c533ba3d8f3a6149accdffea4070dc1 The command finished successfully!
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
OK, I'm doing my best here, but I'm not great at the technical stuff... Port 80 is forwarded to port 81. Sorry, not sure how to run, run commands? Is there a guide, as happy to provide if I have a few pointers? FYI - I use dnsmadeeasy, which I saw mentioned somewhere in this thread for testing if that helps?
-
[Support] Linuxserver.io - NZBHydra v2
I'm trying to migrate from v1 to v2. As per the instructions, I've moved the cfg and db files to the root of the hydra2, but when trying to import, I get the following; [2m2018-02-02 19:26:35.373[0;39m [32m INFO[0;39m [2m---[0;39m [2m[0.0-5076-exec-1][0;39m [36mo.n.migration.FromPythonMigration [0;39m [2m:[0;39m [35m[IP: 10.0.0.39] [0;39mReceived request to migrate from settings file /mnt/user/appdata/hydra2/settings.cfg and database file /mnt/user/appdata/hydra2/nzbhydra.db.* [2m2018-02-02 19:26:35.375[0;39m [31mERROR[0;39m [2m---[0;39m [2m[0.0-5076-exec-1][0;39m [36mo.n.migration.FromPythonMigration [0;39m [2m:[0;39m [35m[IP: 10.0.0.39] [0;39mError while reading old settings file java.nio.file.NoSuchFileException: /mnt/user/appdata/hydra2/settings.cfg at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214) at java.nio.file.Files.newByteChannel(Files.java:361) at java.nio.file.Files.newByteChannel(Files.java:407) at java.nio.file.Files.readAllBytes(Files.java:3152) at org.nzbhydra.migration.FromPythonMigration.migrateFromFiles(FromPythonMigration.java:61) at org.nzbhydra.migration.FromPythonMigration$$FastClassBySpringCGLIB$$25126370.invoke(<generated>) at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:738) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) at org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:99) at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:282) at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96) But as per the screenshot, the files are there and in the right place? Where have I gone wrong?
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
I've upgraded to 6.4.0 from 6.3.5 and in the process, wiped my cache drive with my docker containers. However, I managed to restore, added the HTTPVAL=True, changed port forwarding etc, but on firing up the LE docker, it starts, but I get these messages; ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 50-config: executing... 2048 bit DH parameters present SUBDOMAINS entered, processing Only subdomains, no URL in cert Sub-domains processed are: -d *****.*****.***** E-mail address entered: *****@*****.*** Different sub/domains entered than what was used before. Revoking and deleting existing certificate, and an updated one will be created usage: certbot [SUBCOMMAND] [options] [-d DOMAIN] [-d DOMAIN] ... Certbot can obtain and install HTTPS/TLS/SSL certificates. By default, it will attempt to use a webserver both for obtaining and installing the certificate. certbot: error: argument --cert-path: No such file or directory Generating new certificate Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator standalone, Installer None Obtaining a new certificate Performing the following challenges: Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA. Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA. IMPORTANT NOTES: - Your account credentials have been saved in your Certbot configuration directory at /etc/letsencrypt. You should make a secure backup of this folder now. This configuration directory will also contain certificates and private keys obtained by Certbot so making regular backups of this folder is ideal. ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container Where have I gone wrong, as I bet it's something simple?
-
[Support] Linuxserver.io - SmokePing
Lol, I guess so Didn't try it to be honest and hadn't looked into it before. Thanks for the tip!!!
-
[Support] Linuxserver.io - SmokePing
From someone that migrated from Windows to Linux last year, want my advise, get rid of the safety net of going back to Windows, I tried that before and it does mean you just keep booting it to do so because you know how, commit to MacOS 100% and force yourself to learn how to do it in the new os. It's a rough couple of weeks but far less painful in the long run... I'll be honest, I'm using MacOS at least 90% of the time, but I run one server on Windows and I have to have Parallels for my job, as some of the software I use only runs on Windows. Then I've unraid for the NAS and a few other bits. So I am pretty much all Mac, just a few bits I still need to suss out. For example, a Mac version of Putty for SSH that uses the same commands and also something that refreshes folders better than Finder, as it doesn't update very well and no refresh button. Other than that, I genuinely like Mac. Oh, plus I have an Android phone
-
[Support] Linuxserver.io - SmokePing
Ah ha, a result! I tried on 2 PC's, one on Win 7 and the other on Win 10, but both failed. So I tried on my MAC and it worked! Not sure why, as permissions are the same and I'm using the same user...? But it worked and that's what's important! Thanks for your persistent help though, appreciated! I think it's Windows/SMB/Permissions issues, I don't use Windows so doesn't affect me... I've only been a MAC user for a month, so still finding my way around things, hence still using Windows for stuff until I know how to do it on MAC
-
[Support] Linuxserver.io - SmokePing
Ah ha, a result! I tried on 2 PC's, one on Win 7 and the other on Win 10, but both failed. So I tried on my MAC and it worked! Not sure why, as permissions are the same and I'm using the same user...? But it worked and that's what's important! Thanks for your persistent help though, appreciated!
-
[Support] Linuxserver.io - SmokePing
Nothing showing in the logs for smokeping and other than what's previously mentioned about copying the file or overwriting the file directly, not sure what else I can provide? It does appear to be a permission thing and perhaps I'm doing things in the wrong order, but I'm not sure what else I can do? Does it all work OK for you?
-
[Support] Linuxserver.io - SmokePing
No problem. Here you go... total 40 drwxrwxrwx+ 1 nobody users 148 Feb 4 17:42 ./ drwxrwxrwx 1 nobody users 223 Feb 8 01:01 ../ -rw-r--r-- 1 nobody users 177 Feb 4 17:42 Alerts -rw-r--r-- 1 nobody users 237 Feb 4 17:42 Database -rw-r--r-- 1 nobody users 483 Feb 4 17:42 General -rw-r--r-- 1 nobody users 875 Feb 4 17:42 Presentation -rw-r--r-- 1 nobody users 51 Feb 4 17:42 Probes -rw-r--r-- 1 nobody users 147 Feb 4 17:42 Slaves -rw-r--r-- 1 nobody users 2119 Feb 4 17:42 Targets -rw-r--r-- 1 nobody users 183 Feb 4 17:42 pathnames -rw-r--r-- 1 nobody users 613 Feb 4 17:42 smtp.conf
-
[Support] Linuxserver.io - SmokePing
I stopped the docker, CD'd to the 'smokeping' folder and then typed "chmod 644 Target". I didn't get any confirmation or anything, so tried editing the file directly and copying a changed version of the same file, but no luck. Did I do something wrong? Did this work for you? Thanks.
-
[Support] Linuxserver.io - SmokePing
Apologies for the lack of info. I copied the 'Targets' file out of the folder, edited it using Notepad++ on Windows then tried to copy it back, but received the permission error. I then tried editing the file directly in the appdata folder, but it wouldn't let me save, stating it was being used by another process, even though I had shutdown the docker. Does that help more? Thanks.
-
[Support] Linuxserver.io - SmokePing
Is there anyone able to help us on this? Thanks.
-
[Support] Linuxserver.io - SmokePing
I'm having the same issue. Installed and working perfectly, but I want to update the targets being pinged, but don't have permission to change the file. Anyone any pointers?
-
[Plugin] CA Fix Common Problems
As requested, diagnostics attached... Thanks. Just wondering if anyone with far more knowledgable than me has managed to work out what might be causing the trace issues? Thanks. You should post a new thread in general support where more eyes will see it. No problem, done.
-
[Plugin] CA Fix Common Problems
As requested, diagnostics attached... Thanks. Just wondering if anyone with far more knowledgable than me has managed to work out what might be causing the trace issues? Thanks.
-
[Plugin] CA Fix Common Problems
As requested, diagnostics attached... Thanks. technas-diagnostics-20170201-1648.zip