Replies: 1 comment
-
Found a matching Bug that I believe to the the same issue. #169 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi wanted to check this out for an ambulance company, Loaded a fresh vm with 24.04 installed docker and compose,
downloaded the git setup and ran though the instructions. I can access the login url but entering the login causes it to crash.
the shell spams a bunch of sql errors like
worker-1 | [21:05:53 FTL]
worker-1 | System.Data.SqlClient.SqlException (0x80131904): Invalid object name 'dbo.ScheduledTasks'.
worker-1 | at System.Data.SqlClient.SqlCommand.<>c.b__126_0(Task
1 result) worker-1 | at System.Threading.Tasks.ContinuationResultTaskFromResultTask
2.InnerInvoke()worker-1 | at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
worker-1 | --- End of stack trace from previous location ---
the dbo.xxx changes a but but the similar errors.
Other than that I get some caddy output about ip's
like
caddy-1 | 2025/04/04 21:13:00 http: TLS handshake error from 87.120.126.12:54178: no certificate available for '172.16.193.60'
I am going to assume the 87. address is letsencrypts server and the 172 is a docker virtual ip for a container.
not sure how to resolve this as the config has public urls set and internal lan ip's for the services as the install recommends.
I tried with internal instead of email address and swapping the internal ip's for the public on that appeared to have no effect.
I think there must be an update or tweak need to the container for the sql is my best guess but thats why I am posting here! if any one know where it went wrong its the DEV's !
Beta Was this translation helpful? Give feedback.
All reactions