Problem with OpenServer 6.4.6: Broken domain after changing IP, now stuck in error state #241
Closed
remenikomer
started this conversation in
Discussions
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Environment: OpenServer 6.4.6, Windows 10.
Issue Summary: After changing the IP address for a local domain in the OpenServer panel, the domain became permanently broken, is displayed in red, and the service's internal DNS/DHCP appears to be corrupted.
Steps to Reproduce:
Current Symptoms:
• The domain api.project.local is stuck in a red error state in the OpenServer panel.
• OpenServer no longer adds ANY domains from OSPanel\home\ to the Windows hosts file. The file updates (timestamp changes), but entries are missing.
• Manually adding the domain to hosts is ineffective — OpenServer removes it on restart.
• Deleting the website folder from OSPanel\home\ does not remove the domain entry from the panel. It remains as a red/"ghost" entry.
• Browser requests to the domain resolve to an external/public IP instead of the local server.
• Apache configs in ...\modules\Apache\conf\httpd.conf are auto-rewritten, making manual edits useless.
What Has NOT Worked:
• Resetting OpenServer settings via its options.
• Clearing DNS cache (ipconfig /flushdns, browser DNS).
• Checking the Windows Registry for orphaned entries.
• Renaming the website folder — a new domain appears for the new name, but the old one remains broken in red.
• Error logs (OSPanel\logs) show no relevant entries for this issue.
Core Question: It seems OpenServer's internal configuration or DNS/DHCP service is corrupted. How can I diagnose the root cause or perform a complete reset of its domain/host configuration to fix this?
Beta Was this translation helpful? Give feedback.
All reactions