Jump to content

heratic

Members
  • Posts

    55
  • Joined

  • Last visited

Posts posted by heratic

  1. On 4/19/2020 at 4:47 PM, Exmond said:

    Hello;

     

    For anyone using Slick VPN I was having issues getting the deluge container to work.  The whole issue was with the Slick VPN provided ovpn file.

    In the Slick OVPN file, they offer the ca cert in <ca> blahblah </ca>.  I had to actually download their certificate and update the ovpn file to point to the cert.  Then I was able to start things up.

    Slick OVPN FILE:  https://www.slickvpn.com/locations/

    Slick Cert file: https://www.slickvpn.com/tutorials/using-openvpn-with-ubuntu-mint-network-manager/

    I have started having trouble with my slick vpn. the opvn file has the same key as the SlickVPN.crt in it. getting tls error. Does anyone know how to fix this

     

    2020-05-06 16:02:34,236 DEBG 'start-script' stdout output:
    Wed May 6 16:02:34 2020 SIGHUP[soft,tls-error] received, process restarting

    2020-05-06 16:02:34,236 DEBG 'start-script' stdout output:
    Wed May 6 16:02:34 2020 WARNING: file 'credentials.conf' is group or others accessible
    Wed May 6 16:02:34 2020 OpenVPN 2.4.8 [git:makepkg/3976acda9bf10b5e+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Jan 3 2020

    2020-05-06 16:02:34,237 DEBG 'start-script' stdout output:
    Wed May 6 16:02:34 2020 library versions: OpenSSL 1.1.1f 31 Mar 2020, LZO 2.10

    2020-05-06 16:02:39,237 DEBG 'start-script' stdout output:
    Wed May 6 16:02:39 2020 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

    2020-05-06 16:02:39,238 DEBG 'start-script' stdout output:
    Wed May 6 16:02:39 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]151.236.14.29:443
    Wed May 6 16:02:39 2020 UDP link local: (not bound)
    Wed May 6 16:02:39 2020 UDP link remote: [AF_INET]151.236.14.29:443

     

     

  2. Getting this error starting the docker

     

    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:581:15)
    at Function.Module._load (internal/modules/cjs/loader.js:507:25)
    at Module.require (internal/modules/cjs/loader.js:637:17)
    at require (internal/modules/cjs/helpers.js:22:18)
    at Knex (/opt/nginx-proxy-manager/node_modules/knex/lib/index.js:49:15)
    at Object.<anonymous> (/opt/nginx-proxy-manager/src/backend/db.js:25:33)
    at Module._compile (internal/modules/cjs/loader.js:689:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
    at Module.load (internal/modules/cjs/loader.js:599:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
    at Function.Module._load (internal/modules/cjs/loader.js:530:3)
    at Module.require (internal/modules/cjs/loader.js:637:17)
    at require (internal/modules/cjs/helpers.js:22:18)
    at Object.<anonymous> (/opt/nginx-proxy-manager/src/backend/migrate.js:1:78)
    at Module._compile (internal/modules/cjs/loader.js:689:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10) code: 'MODULE_NOT_FOUND' }
    [app] starting Nginx Proxy Manager...
    [3/4/2020] [11:31:18 AM] [Global ] › ✖ error Cannot find module './dialects/mariadb/index.js' { Error: Cannot find module './dialects/mariadb/index.js'

  3. Hi, I'm considering building a new server. Thinking of going Intel again because AMD is a headache that I can't be bothered dealing with atm as I have 2 kids and a busy life. 

     

    I can't find any solid information online.

     

    Does anyone know if hardware passthrough works on EPYC, like you would expect it to for a server platform or is it like threadripper.

     

    I wouldn't mind building a EPYC system but not if it going to be 6 months of tinkering and never getting to use it. Like my ryzen system that got thrown in the shed for 3 months.

     

    Has anyone Got a EPYC system up and running yet?

  4.  

    On 06/11/2017 at 9:48 PM, amelius said:

    Idk where you heard that, sure, that's what their site *claims* but in reality, it's totally not an issue, you just need to set hypervisor.cpuid.v0  = FALSE and it's all fine. Also, ESXi handles that D3 issue no problem, since you can set the way it handles turning PCI devices on and off. (Tip, if you want to not reboot between using the same GPU, make sure you don't do a forced shutdown on a VM that has a GPU passed through, only a proper shutdown will make it available again for that same (or another) vm without a reboot of the host. If you want a guide that outlines passing through in ESXi, https://www.reddit.com/r/Amd/comments/72ula0/tr1950x_gtx_1060_passthrough_with_esxi/ has a rough outline that works perfectly. I tested it with my configuration and had no issues with getting up and running on both Windows 10 and Ubuntu 16.04 with a GTX 1080 Ti passed through on each one (though on Ubuntu I ran into an annoying login loop i've run into before, but that's just an issue with Xorg and Nvidia drivers not playing nice, not an issue with the passthrough though.)

     

     

    So are you saying you can passthrough GTX geforce cards through on ESXi? I have always read that was not possible.  When did that change?

×
×
  • Create New...