Sedikit Info Seputar
414 Request-URI Too Large nginx/1.4.1 Displaying After Setting Up Blogger Custom Domain? The Solution
Terbaru 2017
- Hay gaes kali ini team Blog Freeday, kali ini akan membahas artikel dengan judul 414 Request-URI Too Large nginx/1.4.1 Displaying After Setting Up Blogger Custom Domain? The Solution, kami selaku Team Blog Freeday telah mempersiapkan artikel ini untuk sobat sobat yang menyukai Blog Freeday. semoga isi postingan tentang
Artikel blogger tips, yang saya posting kali ini dapat dipahami dengan mudah serta memberi manfa'at bagi kalian semua, walaupun tidak sempurna setidaknya artikel kami memberi sedikit informasi kepada kalian semua. ok langsung simak aja sob
Judul:
Berbagi Info Seputar
414 Request-URI Too Large nginx/1.4.1 Displaying After Setting Up Blogger Custom Domain? The Solution
Terbaru
link: 414 Request-URI Too Large nginx/1.4.1 Displaying After Setting Up Blogger Custom Domain? The Solution
Berbagi 414 Request-URI Too Large nginx/1.4.1 Displaying After Setting Up Blogger Custom Domain? The Solution Terbaru dan Terlengkap 2017
Yesterday at BloggersLab, a member of the group complained that after setting up a custom domain for his Blogger blog, he keeps seeing "414 Request-URI Too Large" been displayed whenever he access the URL. I told him to send to me, the login details of his account at where the domain name was registered. He did and I was able to resolve the issue for him.How?
I checked the DNS settings and noticed they were not well configured. I discovered that he only set up two "A" records instead of the four "A" records needed for a Blogger custom domain and also noticed a server provided by the registrar - substituted for one of the four "A" records.
I reconfigured the domain name with the necessary settings and told him to wait while the local DNS server is refreshed. After few minutes, it started working perfectly and his .blogspot.com was successfully changed to his desired .com address.
That's all.
NB: If you notice an error message telling you that "216.239.32.21" doesn't exist, add the remaining server addresses and refresh the page till it saved successfully.
Have you experienced similar problem while trying to set up a custom domain for your blog?
