This problem is solved, the solution was in the browser cache.
But for others, please kindly aware of this.

I was turning this on
[image: image.png]
That was somehow affected the cache.
Everytime I ran py manage.py runserver to 127.0.0.1:8000, I got infinite
loading, since localhost is http://
I knew this after I cleared the cache, and now it works like normal (please
aware that you need to clear cache from browser setting, not by using
ctrl+f5, it didn't work though).
Below is my clear explanation about the case before I got the solution.

--------------------------------

I'm using :

windows 10
vscode
django 3.1
python 3.8.5
chrome latest version

I ran
"py manage.py runserver"
as always,
All was working smoothly like no problems last week.
But suddenly (I don't know exactly when, because I'm working in some
projects), 127.0.0.1:8000 became inaccessible (infinite loading) for this
certain project (one of my project).
[image: image.png]

So I have to change it to localhost:8000

, and it works.
[image: image.png]
(white screen means working).

I don't know why this happened.
I didn't changed any major codes.
Or maybe I did something that I didn't realized was the cause of the
problem. But production seems fine.
I realized that my local url in browser changed to https://127.0.0.1:8000
But the strange thing is, when I changed to http://127.0.0.1:8000, it's
still not working.

I tried in many browsers like chrome, edge, firefox. still same issue.

-----------------------------------------------

My new problem now is,

when I ran 127.0.0.1/sitemap.xml in local, it works like normal.
[image: image.png]
But in production, domain.com/sitemap.xml, I got http error 500.
I'm using heroku, django 3.1, python 3.8.5

Like problem in this link, I've tried the solution, but not working for me.
https://jawaban.online/forum/discuss/97/http-error-500-django-sitemap/

Please kindly help, this sitemap.xml problem got me months of wonder.
Thanks




On Sun, Sep 27, 2020 at 6:49 AM Scott Sawyer <ssaw...@gmail.com> wrote:

> Look in /etc/hosts if you are on a Linux box
>
> Sent from my iPhone
>
> > On Sep 26, 2020, at 11:23 AM, Kasper Laudrup <laud...@stacktrace.dk>
> wrote:
> >
> > Hi Dum Dum,
> >
> >> On 26/09/2020 20.01, dum dum wrote:
> >> I don't know why this happened.
> >> Please advise, Thanks.
> >
> > Try to provide some more details if you want some help.
> >
> > This is most likely related to how you start the server, but since you
> haven't told us how you do that, we can only guess what might be the cause
> of the issue.
> >
> > Consider spending a bit time to write a proper question if you expect
> people to spend time writing a proper answer.
> >
> > Kind regards,
> >
> > Kasper Laudrup
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Django users" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to django-users+unsubscr...@googlegroups.com.
> > To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/eafe28e8-d374-76c4-1222-711b91ac1f35%40stacktrace.dk
> .
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/A3C74021-9D85-4F7E-A6D4-C46049077F3F%40gmail.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CANV3w%3DaW0MxR5YrHC1UuNHkTaP70TDxLTL0%3DDrGCP5WFkWQ7Lg%40mail.gmail.com.

Reply via email to