Error: "Conflicting Server Name"
-
A new (Directus) app that i cloned from an existing one, has seemingly become stuck in an unresponsive (
502 Error) state.The logs show:
[no timestamp] [warn] conflicting server name "<my-app-domain>" on 0.0.0.0:80, ignored [no timestamp] [warn] conflicting server name "<my-app-domain>" on [::]:80, ignored [no timestamp] [warn] conflicting server name "<my-app-domain>" on 0.0.0.0:443, ignored [no timestamp] [warn] conflicting server name "<my-app-domain>" on [::]:443, ignoredHow to resolve this issue?
Note:
- Domain's been configured using a Wildcard config
- Domain has no pending propagation (IPv4 & IPv6 addresses are correctly pointed)
- Tried "Sync DNS" > restart app already
- Have already uninstalled and reinstalled once
Update:
I have again uninstalled the app.
Upon inspecting/etc/nginx/applications/, i can now see 2 orphan configs (for the uninstalled apps) for the concerned <my-app-domain>, which should be the cause of this issue.Is this a bug then (orphaned nginx configs persisting) ?
And for now, should i simply delete those
.conffiles? -
A new (Directus) app that i cloned from an existing one, has seemingly become stuck in an unresponsive (
502 Error) state.The logs show:
[no timestamp] [warn] conflicting server name "<my-app-domain>" on 0.0.0.0:80, ignored [no timestamp] [warn] conflicting server name "<my-app-domain>" on [::]:80, ignored [no timestamp] [warn] conflicting server name "<my-app-domain>" on 0.0.0.0:443, ignored [no timestamp] [warn] conflicting server name "<my-app-domain>" on [::]:443, ignoredHow to resolve this issue?
Note:
- Domain's been configured using a Wildcard config
- Domain has no pending propagation (IPv4 & IPv6 addresses are correctly pointed)
- Tried "Sync DNS" > restart app already
- Have already uninstalled and reinstalled once
Update:
I have again uninstalled the app.
Upon inspecting/etc/nginx/applications/, i can now see 2 orphan configs (for the uninstalled apps) for the concerned <my-app-domain>, which should be the cause of this issue.Is this a bug then (orphaned nginx configs persisting) ?
And for now, should i simply delete those
.conffiles? -
G girish has marked this topic as solved on
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login