cmer

Members
  • Posts

    71
  • Joined

  • Last visited

Posts posted by cmer

  1. 2 hours ago, mrfrogydog said:

    Probably a useful message shown below:

     

    ~# curl -vvv --proxy 10.0.0.200:8118 https://www.google.co.uk
    *   Trying 10.0.0.200:8118...
    * TCP_NODELAY set
    * Connected to 10.0.0.200 (10.0.0.200) port 8118 (#0)
    * allocate connect buffer!
    * Establish HTTP proxy tunnel to www.google.co.uk:443
    > CONNECT www.google.co.uk:443 HTTP/1.1
    > Host: www.google.co.uk:443
    > User-Agent: curl/7.65.3
    > Proxy-Connection: Keep-Alive
    >
    * Recv failure: Connection reset by peer
    * Received HTTP code 0 from proxy after CONNECT
    * CONNECT phase completed!
    curl: (56) Recv failure: Connection reset by peer

     

    So I try to get the page at google.co.uk (via HTTPS) using curl, through the proxy (at 10.0.0.200:8118) which is the one running on my delugevpn container. It feels like there's a simple config problem with the privoxy, or it's not running properly for some reason. The rest of the container itself is accesible, as is the proxy, however the proxy isn't properly dealing with requests.
     

    Worth mentioning also, I have remade the container, tried several versions, completely deleted the config (from appdata), but still have the same problem unfortunately.

    Appreciate any further help if you have the chance.

    Many thanks.

     

    I'm having the same issue. Privoxy only accepts local connections, but not from LAN. It was working perfectly before, something changed in the image. Not sure what...

     

  2. 17 minutes ago, johnnie.black said:

    Tested with Chrome and Firefox, clearing cache didn't help.

    Look in the developer console to see what's happening.

     

    Also try running this on your unraid box:

     

    curl https://raw.githubusercontent.com/cmer/unraid-sanity/master/dynamix-sanity.css -o /usr/local/emhttp/plugins/dynamix/styles/dynamix-sanity.css
    curl https://raw.githubusercontent.com/cmer/unraid-sanity/master/default-sanity.css -o /usr/local/emhttp/plugins/dynamix/styles/default-sanity.css
    

     

  3. 4 hours ago, tucansam said:

    I didn't see that, thanks.  Interesting.  Well at least I'm not alone.  I banged my head into my desk for a little while troubleshooting (see above posts) and decided I would sleep on it.  But now I'm not so sure its me.

    What browser are you using? It works perfectly fine here in Safari, Chrome and Firefox.

  4. 47 minutes ago, tucansam said:

    I followed the instructions in the readme and this is what happened:

     

     

    unraid_big.jpg

    That's actually the new look. You don't like it? 😂

     

    Make sure the CSS is not broken. It looks like something is wrong with it. Or try clearing your browser history.

     

  5. Just now, tucansam said:

    I'm not at home right now, but to me that looks exactly like what I have now.  Either way, I'm not sure how to load new skins or GUIs or whatever you would call it.

    It's based on White but I made many changes. Changes and how to install are in the README.

  6. Guys, I don't think I'll tackle this job at the moment because it basically means starting from scratch. I thought I'd have to make small adjustments only, but the Seafile docker is greatly different from mine. It also does not support the Pro version. If anyone wants to take this over, that'd be great.

     

  7. On 2017-03-25 at 6:34 PM, WuGing said:

    That may well have been part of my problem. I uninstalled, then reinstalled without Pro, and also selected the Share from the get go, and all appears to be working now. May have been a problem with me installing and then changing the Data Path. Did notice in the log it saying it couldn't find a config file. 

     

    Thanks!

     

    This is not really what Seafile is for. It's probably a very bad fit for this use case.

  8. I just want to say THANK YOU to the fine folks at Lime Tech for building such an outstanding piece of software.

     

    I've been using unRAID for close to 2 years now and I am extremely satisfied with the product, the support and the constant improvements made. Keep it up!

     

    • Upvote 1