18 replies
Chris wrote:
Open a web browser and go to http://YOUR-BOX-IP:81 — use the IP address of the machine you installed SparkBox on. Your login was created for you automatically: in the dashboard, open Settings → Service Passwords and find the row labelled Nginx Proxy Manager admin (port 81). It shows your username (admin@sparkbox.local) and the password — copy them in and you're in.
m2elite wrote:
question was their an option where all npm urls are created automaically??
Chris wrote:
Yes, mostly — it is the Custom Domains section in the dashboard Settings. You tick the apps you want and it creates their Nginx Proxy Manager entries (subdomains with SSL) all at once, so you do not build each one by hand. It just needs a domain name already pointing at your box first: set SBDOMAIN in Settings, then tick your apps. Without a domain pointed here NPM has nothing to route, so nothing gets generated on its own.
m2elite wrote:
do not see that option
Chris wrote:
Ah, that's the easy-to-miss bit — it sits under a different tab. In Settings, look at the row of tabs across the top: General, Server Config, Network, Backup, and so on. Click Network, then scroll down a little and you'll find the Custom Domains section. That's the one that creates all your NPM subdomains at once: type your domain into Base Domain, click Load Suggestions, tick the apps you want, then Set Up Selected.
m2elite wrote:
i am getting internal error when creating the cert using cloudflare
Chris wrote:
That's a generic error from the certificate step, not something you've broken. With Cloudflare it's almost always the API token. Two quick checks: first, the token needs Zone - DNS - Edit permission — in Cloudflare that's the 'Edit zone DNS' template, scoped to this domain (a read-only or account-level token can't create the proof record). Second, in the credentials box paste the whole line exactly as the placeholder shows — dnscloudflareapitoken = <your token — not just the token by itself. If it still errors after that, reply here and I'll get Tom's read on the exact failure.
m2elite wrote:
confirmed everything still same internal error
Chris wrote:
I'm sorry this is still stuck after the token steps — you shouldn't have to chase it this far. The 'internal error' just means the certificate step failed; the real reason is one level deeper. Open Nginx Proxy Manager again (the same http://YOUR-BOX-IP:81 address) and click SSL Certificates in the top menu — the failed certificate shows the actual error in red, like 'zone not found' or 'invalid credentials'. Reply with that one line and I'll match it to the exact fix. I've flagged this to Tom as well.
m2elite wrote:
i found the custom domain option it is in the Classic dashboard
Chris wrote:
Nice, glad you found it — and that's a genuinely useful detail, because it suggests the new dashboard doesn't surface Custom Domains in the same place. I'll flag that to Tom. On the Cloudflare cert error, that's still the open piece on my end — whenever you're back in Nginx Proxy Manager, grab the red error line from the SSL Certificates page and I'll finish it off for you.
m2elite wrote:
still getting internal error
m2elite wrote:
i cannot have nginx here and have pi-hole upstream to technium dns
Chris wrote:
That "Internal Error" doesn't tell us the real reason — it's hiding one line deeper in the logs. Run this over SSH: sudo docker logs sb-npm --tail 50, then look near the bottom for the line that actually names the problem (something like "zone not found" or "invalid credentials"). Paste just that line here — skip anything that looks like your Cloudflare token — and I'll tell you the exact fix.
Chris wrote:
Those are three different apps, so let's sort which one you're actually trying to set up. Nginx (NPM) handles custom domains, Pi-hole blocks ads, and Technitium DNS is a separate DNS server — they don't all need to run together for your certificate to work. What's the one thing you want working right now: the custom domain/SSL, or the Pi-hole + Technitium setup? Tell me in a sentence and I'll walk you through just that.
m2elite wrote:
i got npm working outside of tom sparkbox
Chris wrote:
Glad you got it running — a working NPM is what matters. The Cloudflare certificate step inside SparkBox is still the one open piece, and it's with Tom now, so if you ever want to fold it back in I'll post here when there's news. Thanks for sticking with it through all the back-and-forth.