Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Unable to set Wildcard Subdomain

See original GitHub issue

Describe the bug

A clear and concise description of what the bug is.
What version of Nginx Proxy Manager is reported on the login page?

To Reproduce Steps to reproduce the behavior:

Go to ‘Proxy Host’
Click on ‘New Proxy Host’
Scroll down to ‘Domain Names’
Add *.example.com

Expected behavior Unable to add *.example.com

Screenshots This is the example screenshot on your website:

Issue Analytics

State:
Created 3 years ago
Reactions:5
Comments:13

Top GitHub Comments

1reaction

felixgeisslercommented, Nov 3, 2020

I ran into that same bug. Will have to live with a custom config for now…

Edit: I just executed the POST /api/nginx/proxy-hosts manually and it worked.

Sample request in CURL (not tested, since I used Insomnia):

curl 'https://YOUR-NGINX-PROXMANAGER-INSTANCE/api/nginx/proxy-hosts' \
  -H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:83.0) Gecko/20100101 Firefox/83.0' \
  -H 'Accept: application/json, text/javascript, */*; q=0.01' \
  -H 'Accept-Language: en,de;q=0.7,en-US;q=0.3' --compressed \
  -H 'Content-Type: application/json; charset=UTF-8' \
  -H 'Authorization: Bearer YOUR_JWT_HERE' \
  -H 'Origin: https://YOUR-NGINX-PROXMANAGER-INSTANCE' \
  -H 'DNT: 1' \
  -H 'Connection: keep-alive' \
  -H 'Referer: https://YOUR-NGINX-PROXMANAGER-INSTANCE/nginx/proxy' \
  -H 'Cookie: _ga=GA1.2.1959346365.1603901789; _gid=GA1.2.2145157280.1604407981' \
  -H 'Pragma: no-cache' \
  -H 'Cache-Control: no-cache' \
  --data-raw ' \
  { \
    "domain_names": [ \
      "*.YOURDOMAIN.TLD" \
    ], \
    "forward_scheme": "http", \
    "forward_host": "localhost", \
    "forward_port": 8443, \
    "block_exploits": true, \
    "access_list_id": "0", \
    "certificate_id": 0, \
    "meta": { \
      "letsencrypt_agree": false, \
      "dns_challenge": false \
    }, \
    "advanced_config": "", \
    "locations": [], \
    "caching_enabled": false, \
    "allow_websocket_upgrade": false, \
    "http2_support": false, \
    "hsts_enabled": false, \
    "hsts_subdomains": false, \
    "ssl_forced": false \
  }'

Make sure to replace the YOUR-NGINX-PROXMANAGER-INSTANCE, YOUR_JWT_HERE & *.YOURDOMAIN.TLD

1reaction

leimantascommented, Oct 23, 2020

Make folder for data files, mount it and then after creating PROXY sub.domain.com - go to this folder/nginx/proxy_host ; And there you will find generated conf file. Just edit this line: server_name sub.domain.com; into this: server_name *.domain.com;

It works with cloudflare.

And also! You have to create wildcard subdomain cert first.

Top Results From Across the Web

How can I set up a catch-all (wildcard) subdomain? - Domains

How can I set up a catch-all (wildcard) subdomain? · 1. Sign into your Namecheap account. · 2. Select Domain List from the...

Why Is My Wildcard SSL Not Working on a Second Level ...

Again, wildcard SSL certificates ONLY secure subdomains on the designated level. Your issue is that your wildcard SSL isn't working for the subdomains...

Unable to set Wildcard Subdomain · Issue #596 - GitHub

It is possible to add a wildcard certificate through the dedicated SSL Certificates tab. You'll need to do the dns challenge then, so...

Unable to set wildcard subdomains for pages custom domain

I tried to add a wildcard subdomain in the CustomDomain settings of Cloudflare pages as shown below. However, I got an invalid domain...

wildcard dns not working properly [duplicate] - Server Fault

I initially added a wildcard subdomain as below on my cpanel account and it works fine (all level of subdomain works):. *.example.com. but...