Skip to content

macos firewall issues #58

Open
Open
macos firewall issues#58

Description

@pjebs
pjebs
opened on Jan 28, 2021

When I run CompileDaemon -exclude-dir=./container_data -exclude-dir=./.git -exclude-dir=./docker -exclude-dir=./migrations, my go app (local webserver) doesn't seem to work.

When I run go run . I get a macos firewall allow dialog. Once I click "allow", it works.

image

How can I get CompileDaemon to display the firewall dialog?

Activity

  1. pjebs commented on Jan 28, 2021

    @pjebs
    pjebs
    on Jan 28, 2021
    Author

    When I change it to CompileDaemon -exclude-dir=./container_data -exclude-dir=./.git -exclude-dir=./docker -exclude-dir=./migrations -command "go run ." -build="echo 'Running build command\!'",

    The dialog opens up first time. I can click allow. But after a code change, CompileDaemon pauses at this stage:

    2021/01/28 11:20:08 Running build command!
2021/01/28 11:20:08 Build ok.
2021/01/28 11:20:08 Hard stopping the current process..
2021/01/28 11:20:08 Restarting the given command.

    No dialog is shown. The old version of the app is still running.

  2. githubnemo commented on Jan 28, 2021

    @githubnemo
    githubnemo
    on Jan 28, 2021
    Owner

    Sorry I cannot reproduce this as I don't have access to Mac OS X. What you could try is killing the process before making a change and see if the dialog opens up again.

  3. pjebs commented on Jan 28, 2021

    @pjebs
    pjebs
    on Jan 28, 2021
    Author

    How do I do that?

  4. githubnemo commented on Jan 28, 2021

    @githubnemo
    githubnemo
    on Jan 28, 2021
    Owner

    Nevermind, can you try using the command with the -command flag instead of go run? For example:

    CompileDaemon -command=./myserver

  5. sanggonlee commented on Apr 8, 2021

    @sanggonlee
    sanggonlee
    on Apr 8, 2021

    This is still an issue.

    Nevermind, can you try using the command with the -command flag instead of go run? For example:

    CompileDaemon -command=./myserver

    This is how I'm running it. Whatever's given to the -build and -command flags are run every time I make a change, but the changes are not taking effect.

  6. pjebs commented on Apr 8, 2021

    @pjebs
    pjebs
    on Apr 8, 2021
    Author

    I gave up using CompileDeamon. I'm not using any automatic compile application. Just go run . when I want to run.

  7. githubnemo commented on Apr 9, 2021

    @githubnemo
    githubnemo
    on Apr 9, 2021
    Owner

    This is still an issue.

    Nevermind, can you try using the command with the -command flag instead of go run? For example:

    CompileDaemon -command=./myserver

    This is how I'm running it. Whatever's given to the -build and -command flags are run every time I make a change, but the changes are not taking effect.

    And the problem disappears when you disable the firewall? Sorry, I still don't have a mac to reproduce this and there is little to no info as to why this could happen :/

  8. pjebs commented on Apr 9, 2021

    @pjebs
    pjebs
    on Apr 9, 2021
    Author

    Yes

  9. medge-leaflink commented on Jun 20, 2021

    @medge-leaflink
    medge-leaflink
    on Jun 20, 2021

    A bit late to this party but if you are doing ListenAndServe() on a Mac with an address like 0.0.0.0:8080 or :8080 - macOS flags that as intrusive network snooping, hence the warning. Changing your listen address to localhost should solve this issue!

    (I usually have a flag.String() to override and use ./goBinaryHere -host "0.0.0.0" in Docker environments, if that helps)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions