Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Flashpoint fails to start if Internet Information Services is enabled in Windows Features #424

Open
n3tis opened this issue May 17, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@n3tis
Copy link

n3tis commented May 17, 2024

Describe the bug
Flashpoint fails to start if Internet Information Services is enabled in Windows Features.
It displays a msgbox saying "connect ETIMEDOUT 127.0.0.1:12001 [OK]"

To Reproduce
Steps to reproduce the behavior:

  1. Go to appwiz.cpl (or Control Panel > Programs and Features)
  2. Click on 'Turn Windows features on or off'
  3. Scroll down to 'Internet Information Services'
  4. Mark the checkbox, save changes.
  5. Start Flashpoint, receive error message.

Expected behavior
Starting Flashpoint. Oddly enough, I somehow quickly resolved this by just disabling the IIS, because I was testing something previously using it, so my process of elimination quickly deduced it was likely IIS interfering, and turning it off made Flashpoint launch like normal.

Desktop (please complete the following information):

  • OS: Windows 10
  • Flashpoint Version: 12.1 Infinity
  • Log text (if relevant)

Additional context
Personally, I have no issue as I do not need IIS to be enabled, but I thought it is noteworthy that this gets added to some type of wiki so if anyone by any chance has that Windows feature enabled, that they know why their Flashpoint refuses to launch.

@n3tis n3tis added the bug Something isn't working label May 17, 2024
@n3tis n3tis changed the title [BUG] [BUG] Flashpoint fails to start if Internet Information Services is enabled in Windows Features May 17, 2024
@colin969
Copy link
Member

Seems 12001 is used by IIS, you can change this under backPortMin in config.json. It's supposed to iterate up until it can find a port to use but I guess the way it's done isn't clean. May be able to fix that for later release, or change the lowest port default.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants