thekrautboy

joined 1 year ago
[–] [email protected] 1 points 1 year ago

8080 in the case of NC AiO is for not for Nextcloud but for the AiO Container via https.

The Apache port is not internal, but accessible via IP:11000. But it is exclusively for use via reverse proxy.

NC AiO dies things differently than pure NC.

I know NC AiO is a bit weird and unique. But i can only go by what OP is sharing as the compose they are attempting. And none of that makes sense as i said.

to be blunt, and maybe a bit of a jerk, but i think OP did not read the documentation that is linked right in the compose file or the github page. NC AiO has excellent documentation of how to set it up. Thats it, i said it :/

A lot of people are allergic to properly reading documentation and instead they come to places like here and ask others to fix their mistakes.

[–] [email protected] 1 points 1 year ago (2 children)
ports:
  # - 1080:80 # Can be removed when running behind a web server or reverse proxy (like Apache, Nginx, Cloudflare Tunnel and else). See https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md
  - 8080:8080
  # - 8443:8443 # Can be removed when running behind a web server or reverse proxy (like Apache, Nginx, Cloudflare Tunnel and else). See https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md
environment: # Is needed when using any of the options below
  - APACHE_PORT=11000

Whatever you are trying to do there doesnt make sense.

You are telling the Apache webserver that runs inside the container to listen on port 11000, fine. But then you are mapping 8080 to 8080 on the Docker host, how is that supposed to work? And you also mention using NPM, but there is nothing about that visible in the shared compose bit.

Why not simply follow the documentation of Nextcloud, and if you want to combine it with NPM, follow their documentation too?

/r/Nextcloud and /r/NginxProxyManager also exist and are active. This here is not a general techsupport-for-whatever-software subreddit.

And if you have questions about very basic Docker usage, try /r/Docker but i would suggest you simply consult the Docker documentation first.

[–] [email protected] 1 points 1 year ago

Try /r/AdminCraft iirc there is some special panel stuff dedicated to Minecraft hosting.

For general gameserver panels, you could also simply use the search in this sub here.

[–] [email protected] 1 points 1 year ago

Even more so when its by the CEO.

[–] [email protected] 1 points 1 year ago

They are correct tho. This sub is about selfhosting software services. You are asking about a NFC reader board. No need to be shitty about it, you are the one who made the mistake, not them.

[–] [email protected] 1 points 1 year ago

This subreddit was created by a petty and childish troll who made pfSense users look bad by doing nothing on reddit but shitting on a similar open source project. It has been taken over and shut down.

Excellent, well done!

[–] [email protected] 2 points 1 year ago

This sounds so much like an ad.

[–] [email protected] 1 points 1 year ago

Feel free to add more context please or links to other issues.

I did not want to make this a "look how bad Netgate has been for years" post, but mostly focus on this one current issue.

[–] [email protected] 1 points 1 year ago

+1 for deSEC, they are great. Not only do they offer free DNS management but also free "DDNS" subdomains like `example.dedyn.io". One account can manage up to 15 domains in total which should be plenty for most private users, but even if you reach that limit you can contact them and ask nicely for them to increase your allowance. (no promises)

[–] [email protected] 1 points 1 year ago (1 children)

Look at the subreddit sidebar and find the awesome-selfhosted list, search for terms like "ticket" in there and look through the results.

Searching this subreddit for "ticket" is also a good idea.

[–] [email protected] 2 points 1 year ago

I use a subdomain for all my local services.

example.com then local.example.com and for the services service.local.example.com

This way i can still use Lets Encrypt but i also have a clear separation between actual services that are public facing and things i keep local only.

Fitting this to your setup when *.local.example.com points as CNAME to your local reverse proxy, then you can access it fine when at home. When youre away and your laptop tries to access it again, it still retrieves a local IP from the DNS, which of course fails, and because of that your webhoster at example.com doesnt receive any attempts at subdomains etc, you completely bypass it.

[–] [email protected] 1 points 1 year ago

Headache incoming...

view more: ‹ prev next ›