Skip to content
This repository has been archived by the owner on Jan 24, 2023. It is now read-only.

server domain workaround for single server portals #2101

Merged
merged 1 commit into from
May 17, 2022

Conversation

kwypchlo
Copy link
Collaborator

@kwypchlo kwypchlo commented May 17, 2022

explanation and motivation in code description

note: nginx will throw warnings on startup for single server portals but it's expected, it just means there are 2 blocks with the same server name and the latter is going to be ignored (which is a wanted outcome)

nginx            | nginx: [warn] conflicting server name "account.siasky.xyz" on 0.0.0.0:80, ignored
nginx            | nginx: [warn] conflicting server name "siasky.xyz" on 0.0.0.0:80, ignored
nginx            | nginx: [warn] conflicting server name "*.hns.siasky.xyz" on 0.0.0.0:80, ignored
nginx            | nginx: [warn] conflicting server name "*.siasky.xyz" on 0.0.0.0:80, ignored
nginx            | nginx: [warn] conflicting server name "account.siasky.xyz" on 0.0.0.0:443, ignored
nginx            | nginx: [warn] conflicting server name "siasky.xyz" on 0.0.0.0:443, ignored
nginx            | nginx: [warn] conflicting server name "*.hns.siasky.xyz" on 0.0.0.0:443, ignored
nginx            | nginx: [warn] conflicting server name "*.siasky.xyz" on 0.0.0.0:443, ignored

@kwypchlo kwypchlo self-assigned this May 17, 2022
@kwypchlo kwypchlo enabled auto-merge May 17, 2022 12:42
@kwypchlo kwypchlo merged commit df3a33d into master May 17, 2022
@kwypchlo kwypchlo deleted the fix-server-domain branch May 17, 2022 12:56
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants