1. Welcome to LilyPad. Download the project, explore the forums, and create your own LilyPad network.


    If you use the software and enjoy it or have a question, or would like to contribute to the future of the software directly or through resources, please sign up and join our little community.

Proxy Crashing Randomly?

Discussion in 'Support' started by Divomaster, Jun 21, 2014.

  1. Divomaster

    Divomaster New Member

    Hello all,
    I have set up a test server on a Windows 8 PC, but recently I have been noticing that the lilypad proxy has been crashing randomly, with the error message: "Error during AcceptEx tcp: [::] :25565: An existing connection was forcibly closed by the remote host."

    I have try'd multiple versions of the proxy, but the error persists.

    I will post configs etc. if necessary.

    Thanks.
  2. The_Zip

    The_Zip Active Member Resource Contributor

    Its not an issue with how you set it up, its with Go. Though, doing some more research it was patched awhile ago. This issue also only happened to be with Windows 7 from what I have read, though it could be the same with Windows 8 and I have not seen anything about that.

    @Coelho , or I guess anyone familiar with the Jenkins server for LilyPad, what version of Go are you running?
  3. Divomaster

    Divomaster New Member

    I am running version 78 of the proxy software.
  4. Coelho

    Coelho Software Engineer Staff Member Administrator Maintainer

    I'll be updating Jenkins soon towards the latest version of Go which may fix this.

    Everything should work fine on Linux though.
  5. The_Zip

    The_Zip Active Member Resource Contributor

    Yeah, this issue only happens on windows.

    Therefor, @Divomaster , the three options I can think of off the top of my head are a) Waiting the little time for Coelho to update the Jenkins server b) get a small Linux server, a VPS c) Run some type of software that allows you run other softwares on a windows, the easiest I have seen is HERE. Though I have no idea if it will work. You best option in my opinion would to just wait for the Jenkins server to be updated.
  6. Divomaster

    Divomaster New Member

    @The_Zip, I will most likely go with option 1. Thanks for the support.

Share This Page