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

[FEAT] Allow changing listen port #183

Open
1 task done
Gunni opened this issue Oct 31, 2024 · 4 comments
Open
1 task done

[FEAT] Allow changing listen port #183

Gunni opened this issue Oct 31, 2024 · 4 comments

Comments

@Gunni
Copy link

Gunni commented Oct 31, 2024

Is this a new feature request?

  • I have searched the existing issues

Wanted change

Please allow configuration of apache listen port.

Reason for change

I would like to use host networking. I am already using port 80 on the host.

Proposed code change

Accept an environment variable f.ex LISTEN_PORT or HTTP_PORT and use it to configure apache.

Copy link

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

@Roxedus
Copy link
Member

Roxedus commented Oct 31, 2024

The apache config file should reside in persistent storage, you should be able to adapt that file.

@Gunni
Copy link
Author

Gunni commented Oct 31, 2024

The apache config file should reside in persistent storage, you should be able to adapt that file.

Hey that works nicely!

One suggestion then is to allow specifying ip and port, f.ex [::1]:60001 so that the listen port is not trying to expose outward, it works but nc complains about invalid ports every second for the alive check I believe.

nc: service "[::1]:60001" unknown

nc: port number invalid: 127.0.0.1:60001

@LinuxServer-CI
Copy link
Collaborator

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Issues
Development

No branches or pull requests

3 participants