Shamalamadindong

Members
 View Profile  See their activity

  • Posts

    195

  • Joined

  • Last visited

 Content Type 

Posts posted by Shamalamadindong

    Reverse proxy + authentication

    in Lounge

    Posted

    I rather have some page to auth against which will bring up a site with bookmarks to links you're authorized to see

     

    https://github.com/causefx/iDashboard-PHP

     

    Crude but effective if you just need a difference between yourself and everyone else. Not at all secure probably though.

     

    Edit: on the topic of reverse proxy authentication, has any of you seen this?

     

    https://github.com/bitly/oauth2_proxy

     

    Some further reading,

    http://developers.canal-plus.com/blog/install-nginx-reverse-proxy-with-github-oauth2/

    https://jasonbarto.com/authenticate-your-services-with-google-nginx-and-oauth2/ (ignore the ssl warning, hes still using a Startcom cert)

    Advice on new server build

    in Motherboards and CPUs

    Posted

    I know the E5 2670s don't have onboard graphics, which might be an issue because then I'd need a seperate graphics card just for running unRAID... or would I?  I've not tried to actually run it with *no* graphics hardware.  Of course for debugging it'd be useful.

     

    Any motherboard capable of a dual E5-2670 setup will likely have a GPU built in.

    [Support] Linuxserver.io - Apache

    in Docker Containers

    Posted

    I guess I'm not getting the issue. If they insist on using a specific email, why don't you just create it for them? When I did my StartSSL, they would only send to a specific (currently non-existent) address, which I assumed was their way of making me prove I own the domain. I logged into my control panel, created the address they wanted, and presto, everything worked.

     

    Do you not have the ability to create and destroy email addresses at will on your own domain?

     

    My registrar doesn't include email services, i'd have to set up my own mailserver.

     

    To be honest, your problem isn't with Apache or Nginx but with SSL certs.

     

    I have it working now by the way. The Lets Encrypt docker is handling ssl and i'm reverse proxying to the Apache docker through nginx.

    [Request/Done] Let's Encrypt Container

    in Docker Engine

    Posted

    For anyone who would rather stick to Apache but still use Lets Encrypt you can reverse proxy nginx to your existing Apache webserver.

     

        location / {

        proxy_pass http://myapacheip; # my existing apache container
        proxy_set_header Host $host;

        # re-write redirects to http as to https
        proxy_redirect http:// https://;
    }

     

    After that you just have to edit any hardcoded urls to https.

     

    Note, doesn't work if you are routing through Cloudflare, browsers will say there are too many redirects.

    Guacamole, wallabag, Observium, Paperwork (Zuhkov's Docker Template Repository)

    in Docker Containers

    Posted

    I ended up updating it to the latest 0.9.9 and pushed it to my repo on docker hub.

     

    There is no new xml or anything, just edit your existing container settings, and replace the "Repository" setting with "aptalca/guacamole" without the quotes. Leave everything else the same and when you hit save, it will retrieve the images from my repo with 0.9.9 (I installed from scratch, and haven't tried updating an existing install, but it will most likely work)

     

    I only changed the download links in Zuhkov's Dockerfile, nothing else is touched. I have no intentions of maintaining this going forward.

     

    I set it up with one vnc (OS X El Capitan VM) and one rdp (Win10 VM) servers. They both work. But, I had to change one registry setting in Windows because apparently the freerdp package used by guacamole does not yet support the new security setting in Windows. See this page for info: http://boreditguy.com/blog/?p=3784

     

    PS. When you switch to my image, dockerman will get confused and won't delete the old image. You can find that orphan image and delete it manually by opening the advanced view on the docker tab.

     

    Alternatively, you can set up a VM following this excellent guide, https://thatservernerd.com/2016/02/25/install-guacamole-on-centos-76-the-super-easy-way/

    [Support] Linuxserver.io - Apache

    in Docker Containers

    Posted

    cut

     

    I've been agonizing over a response to specific parts of your reply for the last half hour but i think that is going to waste both our times. Suffice to say i did not intent my post to be received in the way it was.

     

    Regarding the Startssl thing, i've been in contact with the live chat however they were unable to help me, they are pointing to my registrar which they say has to "build" my email in to the whois info even though my domains whois states my email as the administrative and technical contact and my registrar is likely to point me at their paid ssl package.

     

    From the way things look right now i think i'm just going to set up a VM and get Apache and Lets Encrypt going manually.

    [Support] Linuxserver.io - Apache

    in Docker Containers

    Posted

    Hold on, relax. Give me a moment to explain my train of thought.

     

    Linuxserver.io - Apache reverse proxy container, there's a guide on how to set this up. However, the maintainers of said container appear to have switched over to a different container also maintained by them based on nginx.

     

    Linuxserver.io - Nginx container, there is no guide on how to set this up and the container is seemingly not preconfigured to use as a reverse proxy. (i don't know anything about nginx so forgive me if its a very simple matter)

     

    aptalca - Lets Encrypt container, based on nginx and based on posts in the support thread, ready to use as a reverse proxy. Maintainer has seemingly joined Linuxserver.io but the container has not been ported over yet. (correct me if i'm wrong on that bit)

     

    My suggestion to rewrite the guide and/or deprecate the apache container was based on the fact that at some point novice users like myself run in to problems, we then head to the support thread for the container and here we learn the maintainers are using an alternative but there's no guide for it. You then have a third option in the lets encrypt container for which there do exist some instructions in the support thread.

     

    Point is, it gets confusing on what is the best option for novice users. When you first start looking in to setting up a reverse proxy you come across your guide first and start trying that. When problems arise however support is made more difficult by the fact the maintainers are no longer using it themselves. As a novice one will naturally drift to the apparently best long term supported option which at the moment in my mind does not appear to be the Apache docker.

     

    Which is why i suggested rewriting the guide to reflect that situation and/or deprecating the apache container.

     

    Please understand, i have a lot of respect for the work you guys do. My suggestion was based entirely in the hopes of making things less complicated for everyone in the long run by preventing people from picking apache today so they aren't faced with a situation where the best option is to switch over and have to redo everything in the future.

     

    I'm really not clear what your point it, but it sounds like you think it's our job to write a guide and/or rewrite a container because you're having issues configuring it?

     

    As i hope i've made clear, my configuration problems are not why i made the suggestion.

     

    Edit: apologies but now that i happen to have your attention, any plans on a Guacamole container?