Closed yeradis closed 7 months ago
Cosmos Server is nearly unusable. I won't switch my default browser just for one website / use-case.
I cannot reproduce this. I might have fixed it in 0.15 without knowing, could one of you try the latest beta version (with :latest-unstable) and let me know if it makes a difference?
I have still a blank page after installing cosmos server with this source code as html
`<!DOCTYPE html>
sorry this doesn't really help atm, did you try with 0.15? (make sure you try with incognito mode to not have cached pages)
I don't know what version is actually running, as you know, I can't login. Even on Firefox my (correct!) credential won't be accepted.
Sorry to say, but Cosmos Server isn't a real solution / alternative for me. Currently I'm running CasaOS for more flexibility and sometimes Portainer (BE) for specific docker container management. I prefer CasaOS for its open port monitoring & management. Cosmos Server just use 80/443 for containers out of the App Store and nothing works without manual editing. In this case, I don't need a web-management platform.
And there is the second issue with Cosmos: I ran Cosmos on my second Raspberry Pi 4 for experimental applications. My main Raspberry runs Home Assistant, AdGuard Home, InfluxDB, Grafana, NGINX Proxy Manager and so on... all very reliable app's. I can't allow my experimental / second Pi to be my proxy for my own domain... so there are a lot of downsides.
Cosmos Server isn't a real solution
Alright thanks for telling me ahead of this block of text that it was not worth answering
Dear development team,
First of all, I'd like to acknowledge the effort that goes into developing a platform like Cosmos Server. I appreciate the challenges involved and the dedication required. However, I feel compelled to address some concerns that have significantly impacted the usefulness of your software in my specific use case.
I've noticed that the software does not perform as expected in key browsers such as Safari. This suggests that comprehensive testing across different browser environments may not have been prioritised sufficiently, resulting in limited accessibility. Ensuring broad browser compatibility is critical to usability and should be a fundamental aspect of quality assurance.
Furthermore, the way in which user feedback and reported problems are handled appears to need improvement. Constructive feedback and problem reports should be seen as opportunities for growth and improvement, not just as criticism. Respectful and open dialogue is essential to building trust and strengthening the community around your software.
I encourage you to view these points as an opportunity to re-evaluate and improve your development and communication processes. Mistakes are understandable, but the response to them is what really makes a difference. An open approach to feedback and transparent communication can greatly improve the quality of your software and the satisfaction of your users.
Thank you for your consideration of my feedback. I look forward to positive developments in the future.
Best regards
Alright dude, thanks for the ChatGPT response. May be it's time for you to take some constructive feedback too: re-evaluate how you interact with people who provide you with hard worked on software for free. You want me to priorities Safari for you with that ass attitude? ... No way!
I will now block you from this repository to prevent this legitimate ticket to further degrade into a ridiculous skirmish.
As I said, I cannot reproduce the issue. This is how far it goes until someone helps me reproduce it, or confirm that it is fixed in 0.15
For anyone struggling to access Cosmos altogether on MacOS: make sure you run without the host mode (see https://cosmos-cloud.io/doc/1%20index/) as it will not work on MacOS
What happened?
First time install and UI does not load at http://localhost/cosmos-ui
What should have happened?
Show Cosmos Setup UI
How to reproduce the bug?
Relevant log output