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

Can't verify Sync. Get no JavaScript error.

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

more options

I've had a working Firefox sync for a little while. I decided that I want to use a different email address so I delete my account from computer and continue to make a new one. When asked to verify, I go to the link and I get a page that says Firefox accounts need JavaScript. I tried opening this link in different browsers and on my phone but same error. Can't get my account verified. Maybe its not important, but my first account was just a forwarding address to what I set my new account email. I.e. my old address was <name>@<domain>.com and my address is <name>@<domain>.ch, the .com forwards to the .CH. Maybe the confuses Firefox sync? And JavaScript is definitely not disabled. I checked aboutconfig.

I've had a working Firefox sync for a little while. I decided that I want to use a different email address so I delete my account from computer and continue to make a new one. When asked to verify, I go to the link and I get a page that says Firefox accounts need JavaScript. I tried opening this link in different browsers and on my phone but same error. Can't get my account verified. Maybe its not important, but my first account was just a forwarding address to what I set my new account email. I.e. my old address was <name>@<domain>.com and my address is <name>@<domain>.ch, the .com forwards to the .CH. Maybe the confuses Firefox sync? And JavaScript is definitely not disabled. I checked aboutconfig.

Giải pháp được chọn

If you copy the url from the email and paste it into the url bar do you receive the same error?

Đọc câu trả lời này trong ngữ cảnh 👍 2

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

more options

Giải pháp được chọn

If you copy the url from the email and paste it into the url bar do you receive the same error?

more options

That worked great. Thank a lot!

more options

Thanks that worked!!!

guigs2 said

If you copy the url from the email and paste it into the url bar do you receive the same error?
more options

For further investigation, was the email formatted differently or which email client did this happen in?

more options

The first time it worked fine with the forwarding address, in the same web mail application.

I have a protonmail account which is a relatively new service interested in easy to use, end-to-end encryption. In this case, I was not using any encryption.

As far as I can tell, the email is formatted HTML, but that seems obvious.

guigs2 said

If you copy the url from the email and paste it into the url bar do you receive the same error?

guigs2 said

For further investigation, was the email formatted differently or which email client did this happen in?
more options

I can confirm this issue. I have protonmail account too.

I can't make sync to work with email address ***@protonmail.com which is an alias to ***@protonmail.ch. I just don't get any verification emails so I have to use ***@protonmail.ch as my email address while sign up. Please do something with it, I am not Switzerland citizen so I would like to use .com domain :)

edit: removed personal information for your protection. (philipp)

Được chỉnh sửa bởi philipp vào

more options

Just to let you know, I've filed a bug at https://github.com/mozilla/fxa-content-server/issues/2653 for us to dig into the issue protonmail accounts.

more options

The folks from protonmail have tracked this down to a bug (present in both Firefox and Chromium/Chrome) in handling of sandboxed iframes. Details are at [1] if you're interested. Protonmail are working on a fix on their side which will hopefully be live in the next few weeks. Copy-pasting the link the from the email should continue to offer a workaround in the meantime.

[1] https://github.com/mozilla/fxa-content-server/issues/2653#issuecomment-119023123