Skip to content

Comments

Dashboard warning "Use IP address to access AxeOS"#1124

Closed
duckaxe wants to merge 2 commits intobitaxeorg:masterfrom
duckaxe:feature/dashboard-messages
Closed

Dashboard warning "Use IP address to access AxeOS"#1124
duckaxe wants to merge 2 commits intobitaxeorg:masterfrom
duckaxe:feature/dashboard-messages

Conversation

@duckaxe
Copy link
Collaborator

@duckaxe duckaxe commented Jul 4, 2025

Discussed #1118

A warning on the dashboard will be displayed if AxeOS is not accessed via IP address.

Bonus: Refactored messages output.

Screenshot 2025-07-04 at 19 41 56

@WantClue WantClue added the design Design Enhancements label Jul 5, 2025
Copy link
Collaborator

@johnny9 johnny9 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this is going to apply anymore after mDNS is implemented or at least it should be updated to mention the .local address.

@duckaxe
Copy link
Collaborator Author

duckaxe commented Jul 6, 2025

@johnny9 You mean, it should trigger a warning if (window.location.hostname.toLowerCase().includes('.local')) ?

@korbin
Copy link

korbin commented Jul 6, 2025

@johnny9 You mean, it should trigger a warning if (window.location.hostname.toLowerCase().includes('.local')) ?

If my API Token PR makes it through, this will not be a necessary recommendation (mDNS .local domains or other FQDNs are OK and preferred.)

@duckaxe
Copy link
Collaborator Author

duckaxe commented Jul 7, 2025

Depends on #1133

@duckaxe duckaxe marked this pull request as draft July 7, 2025 12:13
@duckaxe
Copy link
Collaborator Author

duckaxe commented Sep 11, 2025

Will create 2 separate PRs.

@duckaxe duckaxe closed this Sep 11, 2025
@duckaxe duckaxe deleted the feature/dashboard-messages branch November 4, 2025 08:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

design Design Enhancements

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants