-
Notifications
You must be signed in to change notification settings - Fork 803
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
[!]Invalid Activity with version 0.8.0 #78
Comments
Thanks for reporting this. I'll look into it. |
@misterch0c Did you execute the Merlin Server from an elevated command prompt on the Windows host? If you don't, the server will quit because it can't bind to the port. I see that the last Did you get the same errors running the release versions instead of compiling them? |
Yes, it's an elevated command prompt on Windows: Now for the rest... It seems it was on my side. I just tried again and it worked fine. Only difference is I'm using a VM now vs second laptop earlier... I will let you know if I run into issues again, I need to get my hands on a mac also to try the agent there. |
@misterch0c I'm hoping to be able to duplicate the error you're seeing when running the Merlin Server on Windows. Would you be willing to share the OS version information? Is it possible that something else was already bound to port I'm running |
Please let me know if you have any problems with the Mac (Darwin) agent. I was able to run it on my test Mac without error. |
Environment Data
go build -ldflags "-H=windowsgui -X main.url=https://6.6.6.12:443/" -o merlinAgent.exe cmd/merlinagent/main.go
Expected Behavior
Get stable connection in the server
Actual Behavior
Steps to Reproduce Behavior
Just run it...
Misc Information
Note that I used Linux for the server because the 0.8.0 server automatically shuts down after running on Windows 10 (tried in 2 different desktop, no vm).
I also tried the agent on MacOS and had the same issue (invalid activity).
Downgrading the agent to 0.7 fixed it but then some functionalities were not available.
The text was updated successfully, but these errors were encountered: