Jump to content

IcicleTrepan

Members
  • Posts

    7
  • Joined

Posts posted by IcicleTrepan

  1.  

    19 hours ago, ljm42 said:

    So https://<ipaddress> gives the generic 'ERR_HTTP2_PROTOCOL_ERROR' with no way to get past it? Bummer.

     

    To disable SSL in 6.9.2, you'll need to modify this file on your flash drive:
      config/ident.cfg
    and change:
      USE_SSL="yes"
    to
      USE_SSL="no"
    and reboot.

     

    That has done the trick.  so it seems like SSL was the issue, but how do I fix it?

  2. 6 minutes ago, ljm42 said:

     

    This sounds related to SSL. Can you access the webgui at:

      https://<ipaddress>  (note: https not http)

    (you will need to acknowledge a certificate error in your browser)

     

    If that works, then go to Settings -> Management Access and set "Use SSL/TLS" to No. That should allow you to access the webgui at http://<ipaddress>  (note: http not https)

     

    unfortunately I can't access the webgui with https.  http also appears to be redirecting to https.  maybe there is a way to change that setting from console?

  3. I checked the cables, they seem fine.  Some additional information.  I've tried rebooting the server and the router with no change.  I'm able to watch movies on Plex, even outside of my network and I can access all of my docker containers' web guis just not the one for unraid.  Additionally, I can ping both NIC IP addresses and get replies, so the server appears to be there.  I'm not really sure why I can access everything else but just not the unraid web gui.  I also have mapped network drives on the same server and I can access those no problem.

  4. A couple of days ago my web gui simply stopped loading.  The server has been rock solid for years and I am not exactly sure what happened as I wasn't doing anything with it at the time.  All of the dockers were still up and I can access the command line, I just couldn't access the web gui.  I get the following error in Chrome but it doesn't work in any other web browser either:

     

    This site can’t be reached

    The webpage might be temporarily down or it may have moved permanently to a new web address.

    ERR_HTTP2_PROTOCOL_ERROR

     

    So I tried rebooting the machine and the dockers etc all came back but the web gui is still MIA.  attached is my diagnostic log.

     

    Thanks in advance!

    asgard-diagnostics-20210821-0002.zip

  5. 29 minutes ago, Simon said:

    Thanks. I just went back to that version too and it works again (Q5 at https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md for anyone want to do the same)

     

    43 minutes ago, ThatCanuck said:

    I've been randomly having issues today with PIA, can confirm that it was working well yesterday.  My docker config uses ouroboros to auto update, and it looks like DelugeVPN latest was updated last night. 

     

    Several troubleshooting steps, but the one that worked was to revert to what looks like the previous build in docker.  Can confirm that binhex/arch-delugevpn:2.0.4.dev38_g23a48dd01-2-15 works.

     

    This fixed it for me as well

  6. 3 hours ago, BBenja said:

    First of all thank you for all the effort!

    I use delugeVPN for quite some time now and it worked well. But now I can't conntect to the webUI anymore.

    I only added a new port to the docker (to route the traffice from a different docker). Even though I reversed the change, I stil lcan't connect to the webui. (I use airvpn by the way)

    The log file shows two things. One is just a DEPRECATED message, but the other is the following error:

     

    
    2020-11-29 16:49:03,596 DEBG 'start-script' stdout output:
    Options error: --explicit-exit-notify can only be used with --proto udp
    Use --help for more information.

     

     

    And full log, before it repeats:

    
    2020-11-29 16:49:03,632 DEBG 'start-script' stdout output:
    [info] Starting OpenVPN (non daemonised)...
    
    2020-11-29 16:49:03,637 DEBG 'start-script' stdout output:
    2020-11-29 16:49:03 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-256-CBC' to --data-ciphers or change --cipher 'AES-256-CBC' to --data-ciphers-fallback 'AES-256-CBC' to silence this warning.
    
    2020-11-29 16:49:03,638 DEBG 'start-script' stdout output:
    Options error: --explicit-exit-notify can only be used with --proto udp
    Use --help for more information.

     

    I am having the same problem and I also use AirVPN.  This was working fine for me yesterday.  I can't say for certain as I wasn't paying close attention, however it's possible this may be related to the latest binhex-delugevpn update that I applied this morning.

×
×
  • Create New...