gadget069

Members
  • Posts

    89
  • Joined

  • Last visited

Posts posted by gadget069

  1. I just installed Drop. I can access it on my network, but would like to outside my network as well. I'm using a nginx proxy manager. The login page will load. But after putting in the info the page goes blank. Any ideas? Thanks

     

     

  2. Updated NPM last night now I'm getting a "bad gateway" error

     

    ❯ Starting nginx ...
    ❯ Starting backend ...
    [1/19/2024] [7:29:36 AM] [Global   ] › ℹ  info      Using Sqlite: /data/database.sqlite
    [1/19/2024] [7:29:36 AM] [Migrate  ] › ℹ  info      Current database version: none
    ❯ Configuring npm user ...
    0
    usermod: no changes
    ❯ Configuring npm group ...
    ❯ Checking paths ...
    ❯ Setting ownership ...
    ❯ Dynamic resolvers ...
    ❯ IPv6 ...
    Enabling IPV6 in hosts in: /etc/nginx/conf.d
    - /etc/nginx/conf.d/default.conf
    - /etc/nginx/conf.d/include/assets.conf
    - /etc/nginx/conf.d/include/block-exploits.conf
    - /etc/nginx/conf.d/include/force-ssl.conf
    - /etc/nginx/conf.d/include/ip_ranges.conf
    - /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
    - /etc/nginx/conf.d/include/proxy.conf
    - /etc/nginx/conf.d/include/ssl-ciphers.conf
    - /etc/nginx/conf.d/include/resolvers.conf
    - /etc/nginx/conf.d/production.conf
    Enabling IPV6 in hosts in: /data/nginx
    - /data/nginx/proxy_host/8.conf
    - /data/nginx/proxy_host/7.conf
    - /data/nginx/proxy_host/1.conf
    - /data/nginx/proxy_host/6.conf
    ❯ Docker secrets ...

     

    image.png.5614782f21c4b7054c00f81a96fadc87.png

  3. Still having the same issue. Enabling the vpn tunnel for dockers drops my connection to the server. Luckily I planned for this and had a monitor/keyboard plugged in so i shut that tunnel down. Still looking for advice  on this issue. 

  4. I added a another WireGaurd vpn for a docker. After creating the vpn and confirming it was working, I have lost access to the server. The server shows active in unraid connect, the dockers are still running but am unable to connect to the main server itself. Ugh. I havent tried doing a manual reboot on the server yet. 


    I did a hard reset on the server. It is back up and running going through a parity check.

     

    This is the new tunnel I added for chromium to use that caused all the issues. The tunnel was added to auto start at boot. 

     

    image.thumb.png.ce490aa0f9537e1c45117c906e1add99.png

     

     

     

     

    tortuga-diagnostics-20240110-1459.zip

  5. Trying to understand how this works. I would like to use Wiregaurd for my Chromium docker. For Chromium, the only thing I changed was the network type to wg1. I'm still new to this. I do have a Remote access to Lan setup for my phone and works perfectly. Not sure what I'm missing.

     

    Thanks

     

    image.thumb.png.3064f660a38b8b34de3297242deabd4e.pngimage.thumb.png.7ae311c7bb78c45adafc9f708b13b782.png

  6. I'm having issues with not being abel to create another VPN. I wanted to add another for a docker connection. I have a WG3 I cannot access/edit/delete. I am unable to add any new VPNs. The wg3 is empty. Is there a way to manually delete this?

    image.thumb.png.e4c0f0cd4cc07728d085c2abceeed55f.png

  7. I'm having a wierd docker issue. When trying to start and app, I have started getting a "server error" when trying to start the app. I went to the docker tab and saw the the app had not started, the docker page kepr reloading, the app trying to start the container ID kept changing.  until I did a hard refresh on the webpage, then I can start them without issue. I've had other odd issues with web broiwsers passing through open vpn not working anymore. Not sure why all of a sudden I'm having issues. I'm on 6.12.4. 

    tortuga-diagnostics-20240103-1121.zip

  8. 3 hours ago, ich777 said:

    But that is not my container. I really can't help here since you have to ask in the support thread for the chormium container that you are using.

     

    Maybe you have to forward another port, I'm not that familiar with KasmVNC.

     

    As already said, nothing changed in the last two months for the OpenVPN container.

    Sorry my bad. too many things going at one time, thanks

    • Like 1
  9. 9 hours ago, ich777 said:

    Nothing changed in terms of OpenVPN, the last update that I pushed to it was about two months ago and if it was working in that timeframe then something else must have been changed.

     

    Are you sure that Chromium isn't the culprit? The log that you've attached it not from my container.

     

     

    Here is a snapshot of the log fileimage.thumb.png.2a6e29f187ed1d1087f0be9843828ab8.png

  10. Having issues with OpenVPN. It has worked flawlessly until this evening. Chromium has stopped working properly.  I'm now getting this  error. If I run the browser outside of OpenVPN it works fine

    [custom-init] No custom files found, skipping...
    [ls.io-init] done.
    Obt-Message: Xinerama extension is not present on the server
     2023-12-30 19:07:02,212 [INFO] websocket 0: got client connection from 127.0.0.1
     2023-12-30 19:07:02,217 [PRIO] Connections: accepted: @192.168.1.137_1703984822.212248::websocket
     2023-12-30 19:08:46,400 [PRIO] Connections: closed: @192.168.1.137_1703984822.212248::websocket (Clean disconnection)

     

    Screenshot_20231230_155206_Chrome.jpg

  11. 20 hours ago, Kilrah said:

    That usually means your domains aren't actually configured to resolve to your server anymore, need to fix that. Maybe your ip changed and you haven't set up automatic updating of your DNS records.

    There was an ip address change detected by duckdns.  I restarted duckdns and proxy manager. I've literally havent changed anything since I first got it up and running. 

  12. I believe there was a recent update that I took. I started getting emails that some of my certs were going to expire. I did not take care of them right away. I've tried a few time to update them throught the dashboard and they fail. I'm a complete newb at this stuff.

     

    Quote

    [11/26/2023] [10:31:33 AM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...
    [11/26/2023] [10:32:15 AM] [SSL      ] › ✖  error     Error: Command failed: certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --preferred-challenges "dns,http" --disable-hook-validation  
    Failed to renew certificate npm-50 with error: Some challenges have failed.
    Failed to renew certificate npm-55 with error: Some challenges have failed.
    Failed to renew certificate npm-58 with error: Some challenges have failed.
    Failed to renew certificate npm-65 with error: Some challenges have failed.
    Failed to renew certificate npm-67 with error: Some challenges have failed.
    All renewals failed. The following certificates could not be renewed:
      /etc/letsencrypt/live/npm-50/fullchain.pem (failure)
      /etc/letsencrypt/live/npm-55/fullchain.pem (failure)
      /etc/letsencrypt/live/npm-58/fullchain.pem (failure)
      /etc/letsencrypt/live/npm-65/fullchain.pem (failure)
      /etc/letsencrypt/live/npm-67/fullchain.pem (failure)
    5 renew failure(s), 0 parse failure(s)

     

  13. 54 minutes ago, JorgeB said:

    Those are btrfs checksum errors, a consequence of the device dropping offline before, run a correcting scrub to see if all errors are correctable and if no more ATA errors.

    I've run a scrub 3 times, each time finding errors. 

    image.png.a7fc7a6679547688f18020fd3164307e.pngimage.thumb.png.c607bca678d0bc53aeb93f1c00965204.png

  14. 36 minutes ago, JorgeB said:

    Samsung SSDs are very particular with cable quality.

    The CT500MX is a Cricial drive. I've changed just about every cable, still having issues. My hardware swap was from a 5600g/MSI b450 to a 5950x/MSI b550. My case is a Silverstone CS380. If you have suggestions for good sata cables, that would be appreciated. 

  15. 1 hour ago, JorgeB said:

    First diags show the Samsung SSD dropping offline, seconds one still show ATA errors:

     

    Jul 20 08:42:38 Tortuga kernel: ata5: SATA link down (SStatus 0 SControl 320)
    Jul 20 08:42:39 Tortuga kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
    Jul 20 08:42:39 Tortuga kernel: ata5.00: supports DRM functions and may not be fully accessible

     

    This is usually a cable problem.

    I switched cables again this morning. I do have a sata card in an x16 slot, I wonder if that is casuing issues. But the cache drives are not on that card.

     

    image.thumb.png.ecbda8d92fad99a9e77363f7b2a83614.png