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

Unable to access from public network #775

Closed
happy-Z opened this issue Oct 17, 2023 · 3 comments · Fixed by #777
Closed

Unable to access from public network #775

happy-Z opened this issue Oct 17, 2023 · 3 comments · Fixed by #777

Comments

@happy-Z
Copy link

happy-Z commented Oct 17, 2023

./mtail --progs /usr/local/matil/error_count.mtail --log_dir /usr/local/matil Run on latest version

Only ipv6 ports can be bound,so unable to access from ipv4 public network


INFO:
I1017 17:23:08.063335 3452227 store.go:189] Starting metric store expiry loop every 1h0m0s
I1017 17:23:08.063603 3452227 runtime.go:187] Loaded program error_count.mtail
I1017 17:23:08.063671 3452227 mtail.go:136] Listening on [::]:3904

@jaqx0r
Copy link
Contributor

jaqx0r commented Oct 17, 2023

I'm not sure what you're trying to achieve from your description, but try the --address flag to set the specific IP to bind the listener on.

@happy-Z
Copy link
Author

happy-Z commented Oct 18, 2023

image
It cannot be accessed by public IP because it is only bound to the ipv6 port. My public IP is ipv4.
I hope to be able to access the port bound to ipv4.

@jaqx0r
Copy link
Contributor

jaqx0r commented Oct 18, 2023

I think you want mtail to listen on your IPv4 address. Would you try --address <ipv4> then?

jaqx0r added a commit that referenced this issue Oct 21, 2023
Link to a Go bug about strange dual-stack behaviour.

Fixes: #775
jaqx0r added a commit that referenced this issue Oct 21, 2023
Link to a Go bug about strange dual-stack behaviour.

Fixes: #775
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants