Question

Problem with setup of subdomains in flask

Posted February 3, 2016 7k views
PythonPython Frameworks

Hi
I am trying to setup flask blueprints with subdomains. However it doesnt work.
i have setup my domain to point to the digitalocean dns servers.
I made a created an A record, with @ so i assume that it should cover everything behind the .mydomain.org?

my sample testfile is init.py

from flask import Flask, Blueprint
app = Flask(__name__)
app.config['SERVER_NAME'] = 'mydomain.org'


test = Blueprint('test', __name__)
@test.route("/test")
def testindex():
    return "This is test index page."

app.register_blueprint(test, subdomain='sub')

as described here https://exploreflask.com/blueprints.html

however the result is always ERRNAMENOT_RESOLVED.

Anybody have an idea of what im doing wrong?
Thanks
Best
Bjoern

Add a comment
bjoernoest
By:
bjoernoest
Add a comment

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
1 answer
gparent February 3, 2016

ERR_NAME_NOT_RESOLVED means the domain name you typed in your address bar couldn’t be resolved to an IP address. Without knowing the domain name, there’s very little that can be done to help.

Reply Report
  • bjoernoest February 4, 2016

    okay, thank you. The domain is omicsdb.org, and it works fine with blueprints if i dont use the subdomain part.

    Reply Report
    • gparent February 4, 2016

      Hi,

      I really can’t say anything without the actual, full domain. Your domain works just fine. Are you sure you created the A record?

      EDIT: Even though this isn’t likely to be the problem, have you tried clearing your DNS cache if your computer has one?

      Reply Report
      • bjoernoest February 6, 2016

        Thanks for the answer.
        Sorry for my ignorance, but what do you mean by the full domain?
        So i have omicsdb.org, (which is my maindomain) it is setup as A record, with @ pointing towards my ip 178.62.73.124. The idea is then to have subdomains towards omicsdb.org.

        I have tried two different computers for the same reason.

        Reply Report
        • gparent February 6, 2016

          The only thing you need to do is create an A record named example.omicsdb.org that points to the correct IP and it will work. Presumably you’ve done this, but I have no clue what example is in your case so other than telling you to create the A record correctly, there isn’t much I can suggest. example.omicsdb.org is what I mean by the full domain, so that I could actually verify if it resolves on my side.

          Reply Report
          • bjoernoest March 10, 2016

            thanks, that was my problem, i didnt have an A record, i thought my @ was enough. Now it works.
            Is there any way of making it dynamic, so i dont have to make all the A records, and put everything in the conf file:
            <VirtualHost *:80>
            ServerName fusarium.omicsdb.org
            ServerAdmin youemail@email.com
            WSGIScriptAlias / /var/www/omicsdb/flaskapp.wsgi
            <Directory /var/www/Flaskapp/app/>
            Order allow,deny
            Allow from all
            </Directory>
            Alias /static /var/www/omicsdb/app/static
            <Directory /var/www/FlaskApp/app/static/>
            Order allow,deny
            Allow from all
            </Directory>
            ErrorLog ${APACHELOGDIR}/error.log
            LogLevel warn
            CustomLog ${APACHELOGDIR}/access.log combined
            </VirtualHost>

            Reply Report
Submit an Answer

Related

Looking for something else?

Ask a new question Search for more help