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] "Millennium can't connect...target port '8080' is being used by ' '." #98

Closed
3 tasks done
antitheus185 opened this issue Sep 4, 2024 · 8 comments
Closed
3 tasks done
Labels
bug Something isn't working

Comments

@antitheus185
Copy link

Before Reporting

  • I found no existing issues matching my bug
  • My issue is not caused by the Millennium interface inside Steam (Themes, Plugins & Update Panel). If it is, make a issue report in this repo.
  • My issue is not caused by a theme

Describe the Bug

Bug begins with Millennium first being unable to find something at this link: https://steamloopback.host/appdetails/achievement_progress.json
image
Then at the end of the console in DevTools, there's a lot of connection refused errors - all having to do with source maps and being unable to load them.
image
And the issue is presented with an error pop-up telling me port 8080 is occupied by another process. The only process running on port 8080 when I check in Powershell is steamwebhelper.exe.
image

Expected Behavior

Not really sure, never used this before so I don't know how it should work.

Steps To Reproduce

Follow instructions provided with latest version on Windows 10.
Run steam.exe.

Operating System

Windows

Anything else?

devtools-log.log

@antitheus185 antitheus185 added the bug Something isn't working label Sep 4, 2024
@antitheus185
Copy link
Author

I forgot to mention this in the issue above, but Steam seems to operate normally as long as I do not interact with the pop-up in any way (clicking "OK" or closing it), but I assume it's just vanilla Steam as Millennium couldn't load correctly. Once I interact with the pop-up though, it shuts it down immediately. Not sure if this is helpful in any way for this, just figured I should mention it anyway.

@shdwmtr
Copy link
Owner

shdwmtr commented Sep 4, 2024

This is usually a problem with an antivirus, firewall, or system settings, or even steam settings.

@shdwmtr
Copy link
Owner

shdwmtr commented Sep 4, 2024

#26

Some found success disabling hardware acceleration

@Linx-ESP
Copy link

Linx-ESP commented Sep 4, 2024

[15:55.836] WARN Millennium can't connect to Steam because the target port '8080' is currently being used by 'C:\Program Files (x86)\Steam\steamapps\common\Wildlands\GRW.exe'.
To address this you must uninstall/close the conflicting app, change the port it uses (assuming its possible), or uninstall Millennium.

This happens with Ghost Recon Wildlands too

@shdwmtr
Copy link
Owner

shdwmtr commented Sep 4, 2024

@Linx-ESP in your case, it seems Ghost Recon needs port 8080, while steam also needs it at the same time. To fix that you'll have to change steam's launch args, and add -devtools-port=some-other-port, and launch steam from a separate shortcut then normal. There is nothing I can do about unless you can change the port GRW listens on, because you can't change the one steam is on.

@antitheus185
Copy link
Author

antitheus185 commented Sep 5, 2024

This is usually a problem with an antivirus, firewall, or system settings, or even steam settings.

#26

Some found success disabling hardware acceleration

Ah, good to know. I usually remove Windows Defender when I install Windows to my PC but I didn't this time, gonna do that in a moment to see if it fixes it. If it doesn't, then I'll disable hardware acceleration.

Edit: Strangely enough, it started working without either action taken, I don't know what fixed it or if it was because Windows started with no Internet connection (my USB adapter needed to be reconnected, booting into Linux and then rebooting into Windows causes issues with it) but it seems to be working now. The same source maps errors come up as well as the 404 error, so I assume those have nothing to do with the port error.

@shdwmtr
Copy link
Owner

shdwmtr commented Sep 5, 2024

Those source map errors and 404's are nothing of concern. It should be working perfectly!

@antitheus185
Copy link
Author

Thank you, and it is working perfectly — I've already loaded the Metro skin so far and it's having zero issues. I'm still not sure what caused the bug, and since there's no more issues and the other errors are not related to it, I'll be closing the issue. Thank you again!

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

3 participants