Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

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".

Learn More

SSL_ERROR_BAD_CERT_DOMAIN on signed cert by installed CA

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

more options

I've installed a custom CA certificate and made sure the trust was updated and added the certificate to Apache.

For some reason Firefox doesn't want to accept it, even after I added the name of the domain directly in the alt_names without a wildcard (Hence the "imesa.alpha.kira" as the last record, which is a test)

This works in Chrome without any issues, and used to work in Linux Mint 18.3 without issues (So older version of Firefox about a year ago).

I've attached some screenshots to what I'm doing, this is all on a local server, but added ########### to location info in the cert config, this isn't normally part of it.

Adding the imesa.alpha.kira domain to the common name does work, but I need multiple domains to work.

I'm at a loss as to what could be causing this at this point. Any help is appreciated.

I've installed a custom CA certificate and made sure the trust was updated and added the certificate to Apache. For some reason Firefox doesn't want to accept it, even after I added the name of the domain directly in the alt_names without a wildcard (Hence the "imesa.alpha.kira" as the last record, which is a test) This works in Chrome without any issues, and used to work in Linux Mint 18.3 without issues (So older version of Firefox about a year ago). I've attached some screenshots to what I'm doing, this is all on a local server, but added ########### to location info in the cert config, this isn't normally part of it. Adding the imesa.alpha.kira domain to the common name does work, but I need multiple domains to work. I'm at a loss as to what could be causing this at this point. Any help is appreciated.
Đính kèm ảnh chụp màn hình

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

more options