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.

Solved LilyPadGO Configuration Help

Discussion in 'Support' started by Bowtie, Jan 9, 2014.

Thread Status:
Not open for further replies.
  1. Bowtie

    Bowtie New Member

    When I try and connect servers to LilyPadGo-Connect it doesnt authenticate correctly even though I have given exact information. Here are my configs.

    connect.yml
    Code (text):
    bind: :25556
    logins:
    - username: hub
      password: hubpass
    config.yml for LilyPad-Connect
    Code (text):
    settings:
      address: localhost
      port: 25556
      credentials:
        username: hub
        password: hubpass
     
    What am I doing wrong?
  2. Matt

    Matt Forum Moderator & Contributor Staff Member Moderator Contributor

    Can you give us the full configs? +Proxy.yml and the error please.
  3. Bowtie

    Bowtie New Member

    Hi Matt,
    I currently havent set up the proxy yet. I dont plan on switching to the LilyPadGO until I can actually connect servers to the LilyPadGO-Connect.
    I dont have the error on hand as of now but it went something like this:
    "Could not authenticate server hub: [ip]"
  4. Coelho

    Coelho Software Engineer Staff Member Administrator Maintainer

    Hi there. Please provide us the error that appears in your CraftBukkit server's console. The error above doesn't really seem to be conclusive.
  5. Bowtie

    Bowtie New Member

  6. Coelho

    Coelho Software Engineer Staff Member Administrator Maintainer

    What version of Bukkit-Connect are you running?
  7. Bowtie

    Bowtie New Member

  8. Bowtie

    Bowtie New Member

  9. Coelho

    Coelho Software Engineer Staff Member Administrator Maintainer

    Thanks for the bug report. Commands don't seem to work on windows - I'll fix this asap.
Thread Status:
Not open for further replies.

Share This Page