FusionAuth
    • Home
    • Categories
    • Recent
    • Popular
    • Pricing
    • Contact us
    • Docs
    • Login

    fusioAuth install is damaged?

    Scheduled Pinned Locked Moved
    General Discussion
    0
    29
    83.6k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R
      richb201 @maciej.wisniowski
      last edited by richb201

      @maciej-wisniowski When I try this string I get:

      ERROR 2005 (HY000): Unknown MySQL server host 'database-2.cwymdn16cxes.us-east-1.rds.amazonaws.com/fusionauthdb' (2)

      mysql -h database-2.cwymdn16cxes.us-east-1.rds.amazonaws.com/fusionauthdb -P 3306 -u admin -p

      That is why seeing what a working connection string from the EC2 is would solve the problem.

      1 Reply Last reply Reply Quote 0
      • robotdanR
        robotdan
        last edited by

        ERROR 2005 (HY000): Unknown MySQL server host 'database-2.cwymdn16cxes.us-east-1.rds.amazonaws.com/fusionauthdb'

        That is an invalid host name so that error makes sense. The host is database-2.cwymdn16cxes.us-east-1.rds.amazonaws.com and the database is fusionauthdb.

        R 1 Reply Last reply Reply Quote 0
        • R
          richb201 @robotdan
          last edited by richb201

          @robotdan said in fusioAuth install is damaged?:

          database-2.cwymdn16cxes.us-east-1.rds.amazonaws.com

          What is strange is that I can get into it (RDS mysql) fine from the ec2 directly. I just don't know how that was set up (what connection string is being used)?

          As I think I said, using the path and database name you recommend

          Screenshot from 2021-02-25 21-25-42.png

          Causes a 500 error:
          HTTP ERROR 500

          1 Reply Last reply Reply Quote 0
          • M
            maciej.wisniowski Power User
            last edited by

            Where is your FA instance? On EC2 or localhost? Seems to be localhost from your screen. If so, then can you connect to RDS from the same machine (localhost probably) as one where is your FA instance? Previously you had errors like: "Host '73.188.125.114' is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts'", so maybe it is your localhost IP that is blocked?

            Also, if you get error 500 from FA then you should be able to see more detailed logs on the docker-compose console or using docker-compose logs fusionauth

            R 1 Reply Last reply Reply Quote 0
            • R
              richb201 @maciej.wisniowski
              last edited by richb201

              @maciej-wisniowski thanks for the comment. The fa instance is in EACH container. At least that is my plan. Each container has apache, fa, AWS-CLI, php-fpm, and my application code. The application talks with mysql on RDS just fine. The plan is for fa (in each container) to speak with fusionauthdb which is also up on mysql RDS. So the container on my laptop has its own fa that talks to fusionauthdb on RDS. At least that is the plan!

              I will check to see that I have granted permission to my laptop by putting in the question to AWS support for RDS. I am assuming in 2021 that I don't need to serialize access to the fusionauthdb like we use to be required to do in the old mini days?

              I have a copy running on my laptop for development purposes. I also plan to have a staging server which is just another copy with xdebug and development logging enabled, and finally the actual deployment server. The servers will all be Lightsail.

              1 Reply Last reply Reply Quote 0
              • R
                richb201
                last edited by richb201

                This post is deleted!
                1 Reply Last reply Reply Quote 0
                • R
                  richb201 @maciej.wisniowski
                  last edited by

                  @maciej-wisniowski That was done when we found that there was a bug in

                  #FROM fusionauth/fusionauth-app:1.19.4

                  and we replaced it with:

                  FROM fusionauth/fusionauth-app:1.19.7

                  1 Reply Last reply Reply Quote 1
                  • R
                    richb201
                    last edited by richb201

                    This post is deleted!
                    1 Reply Last reply Reply Quote 0
                    • R
                      richb201
                      last edited by

                      This post is deleted!
                      1 Reply Last reply Reply Quote 0
                      • First post
                        Last post