# Cant use a Subdomain in NGINX Proxy Manager **URL:** \ **Category:** Help\ **Created:** [December 25, 2022, 4:57pm UTC](https://community.letsencrypt.org/t/cant-use-a-subdomain-in-nginx-proxy-manager/190056 "2022-12-25T16:57:59Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Ichhaudich007](https://avatars.discourse-cdn.com/v4/letter/i/e0b2c6/32.png) [@Ichhaudich007](https://community.letsencrypt.org/u/Ichhaudich007)\ **Post date:** [December 25, 2022, 4:57pm UTC](https://community.letsencrypt.org/t/cant-use-a-subdomain-in-nginx-proxy-manager/190056/1 "2022-12-25T16:57:59Z")
i try to set up the NGINX Reverse Proxy Manger on my Docker. Now i have a DynDNS adress and i works with the proxy manager because i can reach the default page of nginx proxy manger over the dyndns adress. When i try to connect a port with the standart dyndns name that i have over the proxy manager it works fine, also with ssl. But when i try to use A subdomain like [subdomain1.laptopsimon.net](http://subdomain1.laptopsimon.net) nothing works i cant create a ssl certificate and i even cant connect over http to the side. Has anybody a Idea why I can not use Subdomains? Also i get this Letsencrypt Error in the LOG: [12/25/2022] [1:50:45 PM] [SSL] › ℹ info Requesting Let'sEncrypt certificates for Cert #9: [subdomain1.laptopsimon.ddns.net](http://subdomain1.laptopsimon.ddns.net) [12/25/2022] [1:50:45 PM] [SSL] › ℹ info Command: certbot certonly --config "/etc/letsencrypt.ini" --cert-name "npm-9" --agree-tos --authenticator webroot --email "[simon.hauber@outlook.de](mailto:simon.hauber@outlook.de)" --preferred-challenges "dns,http" --domains "[subdomain1.laptopsimon.ddns.net](http://subdomain1.laptopsimon.ddns.net)" [12/25/2022] [1:50:49 PM] [Nginx] › ℹ info Reloading Nginx [12/25/2022] [1:50:49 PM] [Express] › ⚠ warning Command failed: certbot certonly --config "/etc/letsencrypt.ini" --cert-name "npm-9" --agree-tos --authenticator webroot --email "[simon.hauber@outlook.de](mailto:simon.hauber@outlook.de)" --preferred-challenges "dns,http" --domains "[subdomain1.laptopsimon.ddns.net](http://subdomain1.laptopsimon.ddns.net)" Saving debug log to /var/log/letsencrypt/letsencrypt.log Some challenges have failed. Ask for help or search for solutions at [https://community.letsencrypt.org](https://community.letsencrypt.org/). See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details. ---
**Author:** ![orangepizza](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/orangepizza/32/19597_2.png) [@orangepizza](https://community.letsencrypt.org/u/orangepizza)\ **Post date:** [December 25, 2022, 7:41pm UTC](https://community.letsencrypt.org/t/cant-use-a-subdomain-in-nginx-proxy-manager/190056/2 "2022-12-25T19:41:24Z")
as its different fqdn youd need to set it separately on nginx RP config as if different domain ---
**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\ **Post date:** [December 25, 2022, 9:42pm UTC](https://community.letsencrypt.org/t/cant-use-a-subdomain-in-nginx-proxy-manager/190056/3 "2022-12-25T21:42:16Z")
Hi @Ichhaudich007, and welcome to the LE community forum 🙂 You first need to have a working HTTP site before you can secure it using `HTTP-01` authentication. Having the web server return a default page is NOT "a working HTTP site". ---
**Author:** ![Ichhaudich007](https://avatars.discourse-cdn.com/v4/letter/i/e0b2c6/32.png) [@Ichhaudich007](https://community.letsencrypt.org/u/Ichhaudich007)\ **Post date:** [January 3, 2023, 9:23am UTC](https://community.letsencrypt.org/t/cant-use-a-subdomain-in-nginx-proxy-manager/190056/4 "2023-01-03T09:23:03Z")
First of all thanks for the replys i now have the main error is that i can not create any porxy host ---
**Author:** ![Ichhaudich007](https://avatars.discourse-cdn.com/v4/letter/i/e0b2c6/32.png) [@Ichhaudich007](https://community.letsencrypt.org/u/Ichhaudich007)\ **Post date:** [January 3, 2023, 9:23am UTC](https://community.letsencrypt.org/t/cant-use-a-subdomain-in-nginx-proxy-manager/190056/5 "2023-01-03T09:23:53Z")
You mean as new host? ---
**Author:** ![orangepizza](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/orangepizza/32/19597_2.png) [@orangepizza](https://community.letsencrypt.org/u/orangepizza)\ **Post date:** [January 3, 2023, 10:15am UTC](https://community.letsencrypt.org/t/cant-use-a-subdomain-in-nginx-proxy-manager/190056/6 "2023-01-03T10:15:01Z")
yes it is but you'd have to fix the container first ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [February 2, 2023, 10:15am UTC](https://community.letsencrypt.org/t/cant-use-a-subdomain-in-nginx-proxy-manager/190056/7 "2023-02-02T10:15:57Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.