Portmaster Service Not Starting Immediately After Boot
Pre-Submit Checklist:
- Check applicable sources for existing issues:
What happened:
Whenever i want to whitelist a domain for an application on Windows, i have to whitelist it too for System DNS Client, otherwise the connection would still be blocked.
I did some research and read that disabling HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dnscache should sort this out and use portmaster as DNS resolver.
I disabled it and everything woks fine, except that now after booting to windows, portmaster would take ~50-70 seconds to start, when booting i can see the tray icon being red and portmaster disabled, doesn't matter how many times i try to enable it just won't. it would start by itself after the mentioned amount of seconds.
What did you expect to happen?:
Use portmaster as DNS resolver and work properly on boot
How did you reproduce it?:
Disable HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dnscache
Also not sure if this is the optimal way to address the thing i wanted to achieve
Debug Information:
Regarding the logs, not sure which ones to post, let me know and i'll share
Greetings and welcome to our community! As this is the first issue you opened here, we wanted to share some useful infos with you:
- π£οΈ Our community on Discord is super helpful and active. We also have an AI-enabled support bot that knows Portmaster well and can give you immediate help.
- π The Wiki answers all common questions and has many important details. If you can't find an answer there, let us know, so we can add anything that's missing.
Can somebody please provide an update or at least a workaround to this?
This issue has been automatically marked as inactive because it has not had activity in the past two months.
If no further activity occurs, this issue will be automatically closed in one week in order to increase our focus on active topics.
Nice, devs ignore issues, stupid bot marks it as stale and eventually close it.
Solving issues by ignoring them, kudos for this approach
I apologize for the delay in responding to your ticket.
Please understand that while we strive to address every report, we must focus first on the most critical issues. Since yours is the only report of this kind so far, it may be specific to your configuration.
In the meantime, you might find it helpful to disable Portmaster v2βs DNS resolver and revert to your systemβs default DNS. Simply remove all DNS server entries from the Portmaster configuration (Note: v2 is still in beta).
Also, application logs might be helpful for us to analyze the issue.
Thank you for your understanding.
This issue has been automatically marked as inactive because it has not had activity in the past two months.
If no further activity occurs, this issue will be automatically closed in one week in order to increase our focus on active topics.
This issue has been automatically closed because it has not had recent activity. Thank you for your contributions.
If the issue has not been resolved, you can find more information in our Wiki or continue the conversation on our Discord.