mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #791] Add support for DNS-01 challenge via the TransIP REST API #669
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#669
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ronaldtveen on GitHub (Dec 25, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/791
I've registered my domain with TransIP, one of the bigger players in the Dutch market when it comes to domain name registration. They have a great API for many of their services, including their DNS.
I have been running a separate docker container with DNSroboCert but would really like to use Nginx Proxy Manager with the DNS-01 challenge so I can keep blocking port 80 on my home router.
The DNS-01 challenge record can be inserted (and removed) via a simple CURL command and a single API key.
The REST API is well documented here:
https://api.transip.nl/rest/docs.html#domains-dns-post
@alexswart commented on GitHub (May 1, 2021):
any news about this i like it to
@chaptergy commented on GitHub (May 9, 2021):
TransIP support was added in https://github.com/jc21/nginx-proxy-manager/pull/942
@poudenes commented on GitHub (Jul 26, 2021):
@ronaldtveen Im trying now to use the DNS challange in NPM but Transip don't know what I mean with this:
certbot_dns_transip:dns_transip_key_file = /etc/letsencrypt/transip-rsa.key
How do I set this?
@ronaldtveen commented on GitHub (Jul 26, 2021):
@poudenes That file is used to identify you when the machine logs in to TransIP to modify the DNS records.
You will need to create a ssh-key on the machine that runs the NginxProxyManager and place those files (private and public) on that machine (choose a logical path yourself), for me that was
/ssl/transip-rsa.keysince I run NPM as a Home Assistant add-on.Then change the path to that file in the config you mentioned.
In your TransIP user profile you can go to the SSH keys page/tab and put the contents of the public key in there.
That should be enough to authenticate NPM with TransIP.
Can’t give too much other support though, I’m also just a regular user of this product.
@poudenes commented on GitHub (Jul 27, 2021):
And do you make the SSL for SSH inside the docker or on the machine where the NPM is running in the docker?
I guess the last one....
@ronaldtveen commented on GitHub (Jul 27, 2021):
Yes, on the machine running NPM and not in the container itself.
The
/ssl/letsencryptdir is where NPM saves its certificates on my machine so I placed the key file one directory up.@poudenes commented on GitHub (Jul 27, 2021):
Probably you need a hosting as well. I only have domain names with TransIP. No option for adding the key
@ronaldtveen commented on GitHub (Jul 27, 2021):
My bad... I checked, and what I believe you should do is go to your Control Panel in TransIP and then go to API under your username profile.
There you should have the option to create a "key pair" by just inputting a description like NPM or whatever.
That returns a key file in plain text. Now copy that to your clipboard and create a
/ssl/transip.keyfile on the server with the copied text.Check/change the path you mentioned in the NPM config to this file, and you should be golden.
No need to create a ssh rsa key on the server itself like I said earlier... didn't remember how I did it before, but this should work.
Good luck!
@poudenes commented on GitHub (Jul 28, 2021):
For those who have same trouble here step by step what to do:
From here you can do the same way you always do to create a SSL.
Only now you enable "Use a DNS Challenge" and select TransIP
If everything went ok the SSL will created... Remeber the subdomain must be point already to your machine!
@Bart-van-Gorp commented on GitHub (Dec 18, 2022):
@poudenes Ik heb mijn web server draaien op ubuntu server. Kun je aangeven wat het exacte commando is om het key path aan te maken? Dit vanaf het begin tot het einde. Ik heb momenteel Godaddy wat niet wordt ondersteund met ssl certificaten en wil overstappen naar TransIP.
@poudenes commented on GitHub (Dec 18, 2022):
Het werkte even. Daarna niet meer. Ik ben geheel overgestapt op clouflare tunnel. Beste keuze ooit. Geen enkele verwijzing is mijn ip nummer zichtbaar
@Bart-van-Gorp commented on GitHub (Dec 18, 2022):
Hoef je voor Cloudflare geen poorten open te zetten? Cloudflare stond ook nog op mijn lijstje om te onderzoeken.
@poudenes commented on GitHub (Dec 19, 2022):
Cloudflare is gratis te gebruiken. Je maakt een tunnel aan en je hebt wel beperkte poorten. Maar ik kan alles benaderen via https en achter de tunnel verwijzen naar alle poorten die de appricaties gebruiken. Ssh poort is te gebruiken.
Ik ben echt onwijs enthousiast.
@Bart-van-Gorp commented on GitHub (Dec 19, 2022):
Dat wordt even stoeien met KPN. De Experiabox V12 is aangesloten op mijn
eigen routers. Momenteel draai ik dus een dubbele NAT op een eigen subnet.
Ik wist helaas niet dat hun V12 niet in bridge modus kon staan. Het is mij
gelukt om de router te vervangen door mijn Deco X60, de echter werkt de
Vlan 4 nu niet via de instellingen van mijn router. Hiervoor dient de
router een speciale proxy tunnel te hebben wat niet lekker werkt. Ook kan dit enkel met PPPOE ipv dhcp
Op ma 19 dec. 2022 07:06 schreef poudenes @.***>:
@poudenes commented on GitHub (Dec 19, 2022):
Zover ik weet gaat alles via Cloudflare over https. Dus als 443 open staat ben je klaar. Achter de schermen op je decide waar cloudflare draait wordt alles intern op interne netwerk doorgezet naar je devices met hun specifieke poorten.
Dus cloudflare is interessant als je aantal applicaties die je vanaf buiten wilt bereiken op een web portal.