Hi Everyone!

I need your help today! 🙏

I have a web-server running on a Windows 10 server machine, with XAMPP for the website. Linux somehow fried my last wifi adapter and I am more at home with windows, however today I found out that NextCloud which is also something I need to install on my server, is not supported on Windows. So I will need to use Docker. The problem is I have zero idea how to use docker. I also already have everything set up so the website is served, but I barely have an idea yet in networking, and I have no idea what NextCloud means when it says reverse proxies and etc.

Here is what I know:

- I have installed Docker Desktop with WSL 2
- I am running Windows 10
- I have a XAMPP server set up on the default ports, running apache and mysql.
- I forwarded the ports 80 and 3389 so I can log in, these are the only open ports as of right now.
- I have Cloudflare set up with CNAMEs to point to my dyndns and it loads my site , but that is all the changes I made to the Default Cloudflare settings, nothing is turned on that it does not offer by default.

Based on this information (and please feel free to ask for more info if needed), I beg you create me a step by step foolproof guide to install NextCloud! 🙏

I really don’t know enough about all this stuff and I am afraid of breaking something even more than I have previously. I will be forever grateful to you if you take the time to help out.

Thank you!

  • ThePossibleDebate@alien.topBEnglish
    1·
    10 months ago

    So I did this using another server on my network using IIS to forward the traffic to the Nextcloud container on my media center running NextCloud AIO. I tried every port but only forwarding requests to the container it set up using port 11000 worked, Have you installed the nextcloud mastercontainer yet? That is where I would begin.

    Without networking knowledge, this is going to probably be difficult for you. Make sure you understand Docker run commands and remember that host.docker.internal works in Docker Desktop for Windows in place of 127.0.0.1. Make sure your mounted volumes correspond to folders in your Windows folders where you’re keeping your data and that you make SURE to mount them with your initial docker run commands.

    Oh, and Docker Desktop is trash for initially starting containers. Try using docker run or, if you like being precise, learn to use docker compose.

    ​

    PS- DO NOT USE IIS FOR YOUR REVERSE PROXY. I am like a crack addict with computer projects and I still don’t know why I chose to remove NGINX on a whim but it was stupid. Even with 14 years of Windows Server knowledge I struggled.