Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Redash
  3. Redash Not Connecting Azure Database for MySQL flexible server

Redash Not Connecting Azure Database for MySQL flexible server

Scheduled Pinned Locked Moved Redash
8 Posts 2 Posters 69 Views 2 Watching
  • 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.
  • W Online
    W Online
    webliska
    wrote last edited by
    #1

    Hello,

    I tried to connect my Azure Database for MySQL flexible server in Redash but it's not getting connected.

    I get an Internal Server Error when I try to Test Connection:

    eada208f-a938-449e-be05-f142742d0363-image.png

    Any help is appreciated.

    Thanks!

    1 Reply Last reply
    0
    • jamesJ james moved this topic from Support
    • jamesJ james marked this topic as a regular topic
    • jamesJ Offline
      jamesJ Offline
      james
      Staff
      wrote last edited by james
      #2

      Hello @webliska
      I moved this topic into the @redash category and made this a normal post.


      Does the logs of the apps reveal anything when trying this?
      Did you make sure that your Cloudron is allowed to connect to the MySQL instance? I hope your MySQL server is not publicly accessible by everyone?

      1 Reply Last reply
      0
      • W Online
        W Online
        webliska
        wrote last edited by
        #3

        When I try to connect nc -v mydb.mysql.database.azure.com 3306 from my Cloudron server to the Azure DB, it connects successfully.

        I did not find any error's in Logs. Can you help me debug this?

        1 Reply Last reply
        0
        • jamesJ Offline
          jamesJ Offline
          james
          Staff
          wrote last edited by
          #4

          Hello @webliska
          nc only checks the ports' availability.
          Unfortunately, I can't provide full support for Azure Database for MySQL.
          But, you should check out the following article https://learn.microsoft.com/en-us/azure/mysql/flexible-server/concepts-networking-public

          From this page:

          Only the IP addresses you allow have permission to access your Azure Database for MySQL Flexible Server instance. By default, no IP addresses are allowed. You can add IP addresses when initially setting up your server or after your server has been created.

          The user that tries to connect is also important. Not every MySQL User is allowed to access the server from anywhere.
          Also, this page: https://learn.microsoft.com/en-us/azure/mysql/how-to-create-users#create-a-nonadmin-user

          Note: on CREATE USER 'username'@'host'.
          In many guides for 'host' the value % is used to allow everything, which is considered a bad practice.
          A good example is here: https://www.digitalocean.com/community/tutorials/how-to-allow-remote-access-to-mysql#step-2-create-a-remote-mysql-user

          Maybe these tips already help you resolve your issue.

          1 Reply Last reply
          0
          • W Online
            W Online
            webliska
            wrote last edited by
            #5

            @james

            Thanks for the links, but the MySQL connection itself is fully working — both inside and outside the container:

            • mysql CLI connects fine using TLS (--ssl-mode=VERIFY_CA)
            • Python’s MySQLdb driver inside the container runs SELECT NOW() successfully
            • TLS handshake works (openssl s_client …)

            So there is no network or credentials problem.

            The actual issue is with Cloudron’s Redash package workers:

            • supervisorctl status shows only workers for periodic emails default queues.
            • Redis queues queries and schemas keep growing (LLEN rq:queue:queries > 0), but no worker consumes them.
            • Redash UI stays stuck at “Query in queue…” because no worker for queries queue is running.

            Normally, Redash workers should be started with:

            QUEUES=queries,schemas,scheduled,emails,periodic,default

            But the Cloudron package doesn’t expose Environment settings in the UI and prevents us from reading /proc/$pid/environ inside the container, so we can’t start a worker manually either (REDASH_COOKIE_SECRET missing).

            This is 100% a packaging/configuration issue with the Cloudron Redash app, not with MySQL or Azure.

            Please update the Redash app to:

            • Start at least one worker for queries,schemas,scheduled,emails,periodic,default queues; OR
            • Expose QUEUES and other REDASH_* env vars in the Cloudron App UI so we can start workers ourselves.

            Until then, any query will remain stuck in the queue because no worker is available to process it.

            So if you can help me with that.

            Thanks!

            1 Reply Last reply
            1
            • jamesJ Offline
              jamesJ Offline
              james
              Staff
              wrote last edited by
              #6

              Hello @webliska
              Thanks for reporting.
              We will look into it.

              1 Reply Last reply
              0
              • W Online
                W Online
                webliska
                wrote last edited by
                #7

                So, how much time do you need, and till then, what can I do for the resolution? Any alternative solutions?

                1 Reply Last reply
                0
                • jamesJ Offline
                  jamesJ Offline
                  james
                  Staff
                  wrote last edited by
                  #8

                  Hello @webliska
                  Unfortunately I can't give you a time estimate and also not offer a different resolution for the time being since I did not have the time yet to reproduce this issue.

                  It would be of great help if you could offer credentials to your MySQL flexible server, so when I start working on this issue, I can work with the same setup minimizing faulty reproduction. (note: please create a different user with access to a different DB. I do not wish to access any of your personal data).
                  If you can do that, please send me a DM with the details.
                  Thanks if advance.

                  1 Reply Last reply
                  0
                  Reply
                  • Reply as topic
                  Log in to reply
                  • Oldest to Newest
                  • Newest to Oldest
                  • Most Votes


                  • Login

                  • Don't have an account? Register

                  • Login or register to search.
                  • First post
                    Last post
                  0
                  • Categories
                  • Recent
                  • Tags
                  • Popular
                  • Bookmarks
                  • Search