.youngspace

Members
  • Posts

    6
  • Joined

  • Last visited

Everything posted by .youngspace

  1. That's really frustrating... Maybe restoring it from another Hard drive where it was originally stored works
  2. I've lost the encryption.key for my Unraid Server, the USB stick is still working and I can boot Unraid, just not decrypt it (I have physical access to my Server ofc). Is there any way to get around this, or is my Data lost?
  3. I tried changing it to bind_addresses: ['0.0.0.0'], sadly the error does not change
  4. @A75G Hi, I followed this guide to install the matrix docker, but I get errors and warnings in the logs, which I cannot find fixes for, can you pls help me? 0: Max number of open files/sockets allowed for this process: 40960 0: Due to the open files/sockets limitation, max supported number of TURN Sessions possible is: 20000 (approximately) 0: ==== Show him the instruments, Practical Frost: ==== 0: TLS supported 0: DTLS supported 0: DTLS 1.2 supported 0: TURN/STUN ALPN supported 0: Third-party authorization (oAuth) supported 0: GCM (AEAD) supported 0: OpenSSL compile-time version: OpenSSL 1.1.1d 10 Sep 2019 (0x1010104f) 0: 0: SQLite supported, default database location is /var/lib/turn/turndb 0: Redis supported 0: PostgreSQL supported 0: MySQL supported 0: MongoDB is not supported 0: 0: Default Net Engine version: 3 (UDP thread per CPU core) ===================================================== 0: Domain name: 0: Default realm: turn.mydomain.tld 0: CONFIGURATION ALERT: You specified --lt-cred-mech and --use-auth-secret in the same time. Be aware that you could not mix the username/password and the shared secret based auth methohds. Shared secret overrides username/password based auth method. Check your configuration! 0: ERROR: CONFIG ERROR: Empty cli-password, and so telnet cli interface is disabled! Please set a non empty cli-password! 0: WARNING: cannot find certificate file: /data/mydomain.cc.tls.crt (1) 0: WARNING: cannot start TLS and DTLS listeners because certificate file is not set properly 0: WARNING: cannot find private key file: /data/mydomain.cc.tls.key (1) 0: WARNING: cannot start TLS and DTLS listeners because private key file is not set properly 0: WARNING: cannot find DH key file: /data/mydomain.cc.tls.dh (1) 0: NO EXPLICIT LISTENER ADDRESS(ES) ARE CONFIGURED 0: ===========Discovering listener addresses: ========= 0: Listener address to use: 127.0.0.1 0: Listener address to use: 172.17.0.19 0: ===================================================== 0: Total: 1 'real' addresses discovered 0: ===================================================== 0: NO EXPLICIT RELAY ADDRESS(ES) ARE CONFIGURED 0: ===========Discovering relay addresses: ============= 0: Relay address to use: 172.17.0.19 0: ===================================================== 0: Total: 1 relay addresses discovered 0: ===================================================== 0: Cannot create pid file: /var/run/turnserver.pid 0: pid file created: /var/tmp/turnserver.pid 0: IO method (main listener thread): epoll (with changelist) 0: Wait for relay ports initialization... 0: relay 172.17.0.19 initialization... 0: relay 172.17.0.19 initialization done 0: Relay ports initialization done 0: IO method (general relay thread): epoll (with changelist) 0: IO method (general relay thread): epoll (with changelist) 0: IO method (general relay thread): epoll (with changelist) 0: turn server id=1 created 0: turn server id=0 created 0: turn server id=2 created 0: IO method (general relay thread): epoll (with changelist) 0: IO method (general relay thread): epoll (with changelist) 0: IO method (general relay thread): epoll (with changelist) 0: IO method (general relay thread): epoll (with changelist) 0: turn server id=4 created 0: turn server id=3 created 0: turn server id=6 created 0: turn server id=5 created 0: IO method (general relay thread): epoll (with changelist) 0: turn server id=7 created 0: IO method (general relay thread): epoll (with changelist) 0: IO method (general relay thread): epoll (with changelist) 0: IO method (general relay thread): epoll (with changelist) 0: IO method (general relay thread): epoll (with changelist) 0: turn server id=8 created 0: turn server id=10 created 0: turn server id=9 created 0: turn server id=11 created 0: IO method (general relay thread): epoll (with changelist) 0: IO method (general relay thread): epoll (with changelist) 0: turn server id=12 created 0: turn server id=13 created 0: IO method (general relay thread): epoll (with changelist) 0: IO method (general relay thread): epoll (with changelist) socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported This server is configured to use 'matrix.org' as its trusted key server via the 'trusted_key_servers' config option. 'matrix.org' is a good choice for a key server since it is long-lived, stable and trusted. However, some admins may wish to use another server for this purpose. To suppress this warning and continue using 'matrix.org', admins should set 'suppress_key_server_warning' to 'true' in homeserver.yaml. -------------------------------------------------------------------------------- Also how exactly can I use postgres as the database and what does that keyserver warning mean? censored_homeserver.yaml
  5. Hello! I just installed a USB 3.0 PCI Card extension into my unraid Server and would like connect an external SSD to the pci card extension, and start a VM via the SSD. If it is possible, to passthrough the expansion card to the VM, while also starting from the SSD, which is connected to that expansion card, that would be great. But if that's too complicated, I'll just buy a second PCI card and pass that one through. On it, there's Ubuntu installed, just in case it matters. I tried following this guide, but by using seaBIOS I always get stuck at "Booting from hard disk..." when starting the vm. https://forums.unraid.net/topic/82092-solved-create-vm-from-bootable-live-usb-drive/ Screenshots of my Unraid VM Settings: Here the yellow marked device is my USB PCI Card, where the SSD is connected to Also I marked, which Disk I set as the "Primary vDisk Location" under the VM settings I'm thankful for any help I can get :)
  6. Hi guys, I tried installing letsencrypt and watched Spaceinvaders Video about that a couple of times now, but I cant manage to get the certificate working... What I'm trying to do is setting up a reverse proxy, so I can use all of my dockers from anywhere. (like storage.youngspace.xyz pointing to the Nextcloud docker or Stations.youngspace.xyz pointing to guacamole). At this point I've set up a DDNS with Namecheap, but it looks like the IP does not automatically update. Im very sure it does have something to do with my Port forwardings or my Domain setup. (I opened Port 1443, 443, 80, 180) I would be very happy if someone could help me letsencrypt log: [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01-envfile: executing... [cont-init.d] 01-envfile: exited 0. [cont-init.d] 10-adduser: executing... ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donate/ ------------------------------------- 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... Variables set: PUID=99 PGID=100 TZ=America/Los_Angeles URL=youngspace.xyz SUBDOMAINS=stations EXTRA_DOMAINS= ONLY_SUBDOMAINS=false DHLEVEL=2048 VALIDATION=http DNSPLUGIN= [email protected] STAGING= 2048 bit DH parameters present SUBDOMAINS entered, processing SUBDOMAINS entered, processing Sub-domains processed are: -d stations.youngspace.xyz E-mail address entered: [email protected] http validation is selected Different validation parameters entered than what was used before. Revoking and deleting existing certificate, and an updated one will be created Generating new certificate /usr/lib/python3.8/site-packages/jmespath/visitor.py:32: SyntaxWarning: "is" with a literal. Did you mean "=="? if x is 0 or x is 1: /usr/lib/python3.8/site-packages/jmespath/visitor.py:32: SyntaxWarning: "is" with a literal. Did you mean "=="? if x is 0 or x is 1: /usr/lib/python3.8/site-packages/jmespath/visitor.py:34: SyntaxWarning: "is" with a literal. Did you mean "=="? elif y is 0 or y is 1: /usr/lib/python3.8/site-packages/jmespath/visitor.py:34: SyntaxWarning: "is" with a literal. Did you mean "=="? elif y is 0 or y is 1: /usr/lib/python3.8/site-packages/jmespath/visitor.py:260: SyntaxWarning: "is" with a literal. Did you mean "=="? if original_result is 0: /usr/lib/python3.8/site-packages/digitalocean/LoadBalancer.py:19: SyntaxWarning: "is" with a literal. Did you mean "=="? if type is 'cookies': Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator standalone, Installer None Obtaining a new certificate Performing the following challenges: http-01 challenge for stations.youngspace.xyz http-01 challenge for youngspace.xyz Waiting for verification... Challenge failed for domain youngspace.xyz Challenge failed for domain youngspace.xyz Challenge failed for domain stations.youngspace.xyz http-01 challenge for youngspace.xyz http-01 challenge for stations.youngspace.xyz Cleaning up challenges Some challenges have failed. IMPORTANT NOTES: - The following errors were reported by the server: Domain: youngspace.xyz Type: connection Detail: Fetching http://youngspace.xyz/.well-known/acme-challenge/ps1sdQlZOvddALe_-cWAA_fPzt78aLvDmFwxQHqUUc4: Error getting validation data Domain: stations.youngspace.xyz Type: connection Detail: Fetching http://stations.youngspace.xyz/.well-known/acme-challenge/a8ULSr2_IHrC2rKuYckXmwU93d_ZuOgInKhPX8ms41w: Timeout during connect (likely firewall problem) To fix these errors, please make sure that your domain name was entered correctly and the DNS A/AAAA record(s) for that domain contain(s) the right IP address. Additionally, please check that your computer has a publicly routable IP address and that no firewalls are preventing the server from communicating with the client. If you're using the webroot plugin, you should also verify that you are serving files from the webroot path you provided. - 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