Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Tìm hiểu thêm

I just upgraded to Firefox Quantum 57.0 I am now getting "The page isn't redirecting properly." messages from several sites that were all working fine before

  • 12 trả lời
  • 1 gặp vấn đề này
  • 1 lượt xem
  • Trả lời mới nhất được viết bởi Matthew Slyfield

more options

I've verified that cookies are not disabled or restricted.

I've tried deleting existing cookies and history.

All to no effect.

I've verified that cookies are not disabled or restricted. I've tried deleting existing cookies and history. All to no effect.

Tất cả các câu trả lời (12)

more options
more options

I don't use any of the security software you mentioned.

Aside from that, the sites all loaded fine in the prior version of Firefox. I only started having a problem after the upgrade to 57.0

more options

Did you check the links I posted?

more options

Yes. The sites that I am having the problem with work fine in IE and Chrome, and they worked fine in the previous version of Firefox.

The problem is not site home pages not loading, I am getting a specific error message regarding redirection issues on internal links between one page and another on a given site.

Yes, I looked at all of your links. None of them address the specific error I am getting: The page isn't redirecting properly.

more options

Start Firefox in Safe Mode {web link} by holding down the <Shift> (Mac=Options) key, and then starting Firefox.

A small dialog should appear. Click Start In Safe Mode (not Refresh). Is the problem still there?

more options

If clearing cookies didn't help then It is possible that the cookies.sqlite file in the Firefox profile folder that stores the cookies got corrupted.

  • rename/remove cookies.sqlite (cookies.sqlite.old) and if present delete cookies.sqlite-shm and cookies.sqlite-wal in the Firefox profile folder in case cookies.sqlite got corrupted.

You can use the button on the "Help -> Troubleshooting Information" (about:support) page to go to the current Firefox profile folder or use the about:profiles page.

more options

FredMcD said

Start Firefox in Safe Mode {web link} by holding down the <Shift> (Mac=Options) key, and then starting Firefox. A small dialog should appear. Click Start In Safe Mode (not Refresh). Is the problem still there?

Yes, the problem is still there in safe mode.

more options

cor-el said

If clearing cookies didn't help then It is possible that the cookies.sqlite file in the Firefox profile folder that stores the cookies got corrupted.
  • rename/remove cookies.sqlite (cookies.sqlite.old) and if present delete cookies.sqlite-shm and cookies.sqlite-wal in the Firefox profile folder in case cookies.sqlite got corrupted.

Tried that, and it had no effect.

more options

Maybe try a refresh? Or like others are saying a Anti-Virus program, Or do you have any type of child or webpage blocking sometimes thats how they block pages.

Thanks.

more options

Can you post a link to a publicly accessible page (i.e. no authentication or signing on required)?

What does the Network Monitor show as the HTTP response headers?

more options

plp050452 said

Maybe try a refresh? Or like others are saying a Anti-Virus program, Or do you have any type of child or webpage blocking sometimes thats how they block pages. Thanks.

Refreshing doesn't work.

With Chrome and IE not having an issue and the issue only popping up in Firefox after upgrading to version 57.0, in my mind that rules out anti-virus or anything else external.

more options

cor-el said

Can you post a link to a publicly accessible page (i.e. no authentication or signing on required)? What does the Network Monitor show as the HTTP response headers?

https://armorgames.com/

I couldn't tell. The site is add supported and graphics heavy. With all the individual call to load PNGs it generates too much data and scrolls off too quickly to tell. I couldn't find a way to write the output off to a file.