Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Change default port used instead of 8080
See original GitHub issueWhere are the configurations stored after snap install microk8s --classic? I don’t find it in /etc or my home folder. I would like to run the cluster on different port so as not to clash with various native applications using 8080. Thanks.
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Are there good alternative HTTP ports rather than port 80?
When port 80 is used for one address/webserver, it's fairly common to ... There are actually 3 HTTP alternative ports: 591, 8008 and...
Read more >Port Authority, for Internet Port 8080
Its use in a URL requires an explicit "default port override" to request a web browser to connect to port 8080 rather than...
Read more >Changing the Port Number from 8080 - Tomcat
Just change the port attribute from 8080 to 80, and restart Tomcat. Unless that port number is already in use or you lack...
Read more >How To Change Port Number in Apache in Ubuntu
Here are the steps to change port number in Apache in Ubuntu from 80 to 8080. 1. Open Apache Config File. Open terminal...
Read more >Change default port used instead of 8080 · Issue #198
I would like to run the cluster on different port so as not to clash with various native applications using 8080. Thanks.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi @jareks,
We recently completely removed the insecure 8080. All communication now goes through the secure port 16443. Please review all open ports at [1]
If you need the insecure port 8080 back (or configure it) you need to edit
/var/snap/microk8s/current/args/kube-apiserverand restart MicroK8s (microk8s.stop; microk8s.start)[1] https://github.com/ktsakalozos/microk8s.io/blob/docs/ports-rework/docs/ports.md
That makes perfect sense. Indeed, with clean install everything works as intended. Thanks for your help and patience!