Skip to content
This repository has been archived by the owner on Sep 12, 2024. It is now read-only.

Wildcard subdomain not working? #46

Open
unisqu opened this issue Oct 6, 2018 · 7 comments
Open

Wildcard subdomain not working? #46

unisqu opened this issue Oct 6, 2018 · 7 comments

Comments

@unisqu
Copy link

unisqu commented Oct 6, 2018

i tried adding
rpush frontend:*.example.com example http://123.123.123.123:80

it's not working. doesnt seem to check anything with lrange when i did monitor on redis

@unisqu
Copy link
Author

unisqu commented Oct 8, 2018

hello?

@cezarsa
Copy link
Member

cezarsa commented Oct 9, 2018

Wildcards are currently not supported as frontend entries, only as tls certificates.

@unisqu
Copy link
Author

unisqu commented Oct 10, 2018

what a shame, this is a good piece of software. I'll improve on it. but before that, is there an alternative that uses golang other than traefik u will recommend?

@unisqu
Copy link
Author

unisqu commented Oct 10, 2018

also, where should i modify the the *.example.com <- frontend? any hints? i can code myself and add to this.

@cezarsa
Copy link
Member

cezarsa commented Oct 11, 2018

You should set an explicit hostname without wildcards, as in:

redis-cli rpush frontend:mywebsite.example.com mywebsite http://123.123.123.123:80

@unisqu
Copy link
Author

unisqu commented Oct 12, 2018

i need wildcards. I will modify the planb code myself. pls drop a hint where that file line is so i can work on it.

@cezarsa
Copy link
Member

cezarsa commented Oct 18, 2018

The best approach would probably be by modifying the backend logic to query redis for a wildcard key here inside this if statement:

planb/backend/redis.go

Lines 138 to 140 in 5d26837

if len(backends) < 2 {
return "", nil, nil, ErrNoBackends
}

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants