celenity/Phoenix
8
198
Fork
You've already forked Phoenix
18

[OTHER] Secure Connection Failed to https://phoenix.celenity.dev/issues #320

Closed
opened 2026年06月15日 15:46:55 +02:00 by fossil535 · 3 comments

Please explain your inquiry.

Phoenix Issue Tracker linked from Firefox Help navigates to https://phoenix.celenity.dev/issues

This is showing up as a security risk today because of error - SSL_ERROR_RX_RECORD_TOO_LONG

### Please explain your inquiry. Phoenix Issue Tracker linked from Firefox Help navigates to https://phoenix.celenity.dev/issues This is showing up as a security risk today because of error - SSL_ERROR_RX_RECORD_TOO_LONG
fossil535 changed title from (削除) [OTHER] (削除ここまで) to [OTHER] Secure Connection Failed to https://phoenix.celenity.dev/issues 2026年06月15日 15:47:32 +02:00
Contributor
Copy link

I can't reproduce that issue.

@fossil535, do you using latest/upstream Firefox/Phoenix versions?

I can't reproduce that issue. @fossil535, do you using latest/upstream Firefox/Phoenix versions?

Strange - I'm unable to replicate this as well.

@fossil535 Can you please confirm if this is still an issue? It may have just been something wrong on the server side earlier (that they now may have fixed).

Strange - I'm unable to replicate this as well. @fossil535 Can you please confirm if this is still an issue? It may have just been something wrong on the server side earlier *(that they now may have fixed)*.

@koru @celenity found out the issue.

I have been using Control D as my DNS resolver for more than a month now and have set my DNS server to Luxembourg.

Have been trying to verify if I get better cookie notices with an option to reject.

The URL https://phoenix.celenity.dev/issues was working correctly a week or so back. Checked yesterday and saw this problem.

Setup a redirect rule to send across my actual location and now it is working as expected.

I am always on the most recent Phoenix build.

But this appears to be some check on the server side which is sending a bad certificate back.

Closing the bug for now. Will share if I find the error.

@koru @celenity found out the issue. I have been using Control D as my DNS resolver for more than a month now and have set my DNS server to Luxembourg. Have been trying to verify if I get better cookie notices with an option to reject. The URL https://phoenix.celenity.dev/issues was working correctly a week or so back. Checked yesterday and saw this problem. Setup a redirect rule to send across my actual location and now it is working as expected. I am always on the most recent Phoenix build. But this appears to be some check on the server side which is sending a bad certificate back. Closing the bug for now. Will share if I find the error.
Sign in to join this conversation.
No Branch/Tag specified
dev
pages
2026年07月08日.1
2026年06月10日.1
2026年05月21日.2
2026年05月21日.1
2026年04月27日.1
2026年03月31日.1
2026年03月30日.1
2026年02月23日.1
2026年02月16日.1
2026年01月21日.1
2025年12月23日.1
2025年11月27日.1
2025年11月07日.1
2025年10月26日.1
2025年10月12日.1
2025年10月03日.1
2025年09月07日.1
2025年08月06日.1
2025年07月30日.1
2025年07月11日.1
2025年06月24日.1
2025年06月12日.1
2025年06月10日.1
2025年06月06日.1
2025年06月02日.2
2025年06月02日.1
2025年05月11日.1
2025年04月27日.1
2025年04月15日.1
2025年04月11日.1
2025年04月02日.1
2025年03月25日.1
2025年03月20日.1
2025年03月12日.1
2025年03月05日.1
2025年02月28日.1
2025年02月21日.1
2024年02月18日.1
2025年02月14日.1
2025年02月13日.1
2025年02月01日.1
2025年01月30日.1
2025年01月27日.1
2025年01月24日.1
2025年01月22日.2
2025年01月22日.1
2025年01月20日.2
2025年01月20日.1
2025年01月19日.1
2025年01月14日.1
2025年01月13日.1
2025年01月12日.2
2025年01月12日.1
2025年01月06日.1
05January2025v1
20240103.2
20250103.1
20241229-1
20241225-1
20241216-1
20241211-1
20241204-1
20241203-1
31November2024v1
20241103-1
20240924-1
20240914-1
20240907-1
20240902-1
20240831-1
20240825-1
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
celenity/Phoenix#320
Reference in a new issue
celenity/Phoenix
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?