i am having an issue to map my django app to my domain even though i did everything correctly, i even added the ip in my hostinger panel, to match but when i visit my domain "BLANK!!!!". the app is running on django which is running on docker
#🔒 django.domain problem
129 messages · Page 1 of 1 (latest)
@indigo gate
Remember to:
- Ask your Python question, not if you can ask or if there's an expert who can help.
- Show a code sample as text (rather than a screenshot) and the error message, if you've got one.
- Explain what you expect to happen and what actually happens.
:warning: Do not pip install anything that isn't related to your question, especially if asked to over DMs.
Closes after a period of inactivity, or when you send !close.
anyone
helo!!!!!!! any one here that can debug this ?????
woah!!! no one guess i unlocked a rare scenario lol
?
your port is 8000
web browsers connect to port 80 by default, not 8000
if you visit yourdomain.com:8000 do you see it
Nope
Tried different browsers
Too
maybe it's just that the dns changes take a while to propagate
Is it?
How long?
Running me ec2 for a day? Dammnn
what is your domain?
It'll expire next Jan
Yes I saw the server, it means it's correct, don't know why it isn't showing then???
the IP in your image is 13.220.132.164
the one here is different
Yeah i know cuz I rebooted the instance
So it's the new one
The image one was old
I turned of the server
i... okay
*or 443 for Https, 80 is only for http
Also can you actually run the server so we can debug this?
it doesnt work no matter what i do
ok wait
i treid running nginx which runs on https, it still didnt worked
Tell me when you setup the server, and show the IP
Yep, it now does point to the domain
but the domain is not showing the app
Let me launch my test tool to browse it
while it is pointing to the server
ok sure
sure
Also what device you are using?
also the ip is working well and good
windows
youre using custom forward proxy ??
name ??? of the proxy
how ?????
still aint working for me
ok tell me your browser name
dude you there ???
This is working probably
Just because it is not HTTPS, it complain
Oh I launch it from burp test suite so I can see more things
all the browsers i have by default switch to https no mtter the link
ill try from there
Try remove the s in https
And then tell the browser to ignore the fact that it is http and unsafe
Also the third issue might be DNS caching which I couldn't find a utility in windows that easily check this
no no the server is running on linux
DNS caching might apply on both your device and the DNS server you resolving
my bad oops i thought you asked my machene
No, just your personal device
ohh
And also the DNS server
Since you set ttl to 14400
Which basically say:
Btw this record is valid for 4h so you don't have to check again for the next 4h
how to do that 🥲
I think it would show you a warning page
And you can click continue anyway and something like that
showed nothing
Screenshot
Well, your domain isn't HSTS so hmm
Your server might still serve response even tho it is HTTPS protocol, but since it cannot serve HTTPS response, it return some invalid thing that browser cannot read ig
i guess hsts is forced in my browsers
Well, browser will attempt https upgrade if possible
Probably
havent treid it
Or setting up certificate automatically with nginx might be easier
For context, basically setup ACME and request Let's Encrypt to verifyLet's Encrypt would issue a certificate to you and nginx will automatically apply it
appreciate it
It might require the port to be 443/80 (public facing)
Which should be configurable on nginx
will try it
This help channel has been closed. Feel free to create a new post in #1035199133436354600. To maximize your chances of getting a response, check out this guide on asking good questions.