Open MLNW opened 8 months ago
Not seen that before, what do you have in your .env?
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
Not seen that before, what do you have in your .env?
APP_URL=https://heimdall.my.domain
FORCE_HTTPS=true
Sorry for the long delay. These are the values in my .env. The FORCE_HTTPS
one needs to be there otherwise we get errors in the browser regarding a mix of HTTP
and HTTPS
traffic. The instance sits behind a reverse proxy that handles SSL termination.
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
@MLNW did you ever find a fix for this, I have the same issue.
No, I did not find a solution but I also haven't looked at it since my last comment.
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
I still have this issue and I may decide to just wipe it and start from scratch unfortunately.
The logs OP gives is that it's unable to connect to mysql, are yours the same?
Having this same problem. connection refused / mysql
SQLSTATE[HY000] [2002] Connection refused (Connection: mysql, SQL: select table_name as `name`, (data_length + index_length) as `size`, table_comment as `comment`, engine as `engine`, table_collation as `collation` from information_schema.tables where table_schema = 'forge' and table_type in ('BASE TABLE', 'SYSTEM VERSIONED') order by table_name)
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
Hello. Same issue here, connection refused.
Hello. Same issue here, connection refused.
relatively easy workaround: add the 2.5.8 tag and export from the settings page. then start a new install and import everything. not sure what you lose but it helps.
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
2.6.0 updated the underlying Laravel version from 8 to 10, so it's possible old configuration files are interfering. Maybe try a new install and copy the database across (if using sqlite) or point to the old database.
I host Heimdall on a Kubernetes cluster. It is running in version 2.5.8 but when I upgrade to 2.6.0 or 2.6.1 the browser shows
In the container I see the same errors spammed quite frequently:
I'm surprised to see
mysql
here. Did I miss an upgrade step?