mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 15:05:57 +03:00
[GH-ISSUE #1517] After update 0.15.11 #2892
Labels
No labels
In Process
bug
bug
dev-triage
documentation
duplicate
enhancement
fixed
good first issue
help wanted
integration
invalid
pull-request
question
requires agent update
security
ui tweak
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tacticalrmm#2892
Loading…
Add table
Add a link
Reference in a new issue
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?
Originally created by @MAJINFORMATIQUE on GitHub (May 19, 2023).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1517
Server Info (please complete the following information):
Installation Method:
Describe the bug
After last update error 500 on restart. It seems that 2 new datafied appears in database without their value type (word, varchar, other) : first one is core_coresettings.open_ai_token and the second is core_coresettings.open_ai_model.
Could you send this values?
@dinger1986 commented on GitHub (May 19, 2023):
Can you try update again?
update.sh --forceIt might help!
Leaving this as an issue so @sadnub and @wh1te909 can have a quick look later on today.
@darouca commented on GitHub (May 19, 2023):
Hi.The same here. On 19 May 2023, at 04:34, dinger1986 @.***> wrote:
Can you try update again?
update.sh --force
It might help!
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>
CONFIDENCIAL. SUJEITO A PRIVILÉGIO LEGAL DE COMUNICAÇÃO, PROTEGIDO NOS TERMOS DA LEI. Esta mensagem e seus anexos são endereçados exclusivamente para seu destinatário e podem conter informações confidenciais ou privilegiadas e legalmente protegidas, sujeitas a sigilo profissional. Se você não é o destinatário ou uma pessoa autorizada para recebê-la, você não deve usar, copiar, divulgar ou tomar qualquer ação com base nesta mensagem ou quaisquer informações nela contidas. Se você recebeu esta mensagem por engano, por favor, informe o remetente imediatamente, respondendo o e-mail e exclua esta mensagem do seu computador. O conteúdo desta mensagem e seus anexos não necessariamente expressão o parecer ou a intenção da empresa não implicando qualquer obrigação legal ou responsabilidades. Ao trocar mensagens, fica ciente que ferramentas, nacionais e internacionais, de monitoramento e analise são utilizadas.--------------------------------------CONFIDENTIAL. SUBJECT TO LEGAL PRIVACY OF COMMUNICATION, PROTECTED IN TERMS OF LAW. This message and its attachments are addressed exclusively to its recipient and may contain confidential or privileged and legally protected information, subject to professional secrecy. If you are not the recipient or a person authorized to receive it, you must not use, copy, disclose or take any action based on this message or any information contained therein. If you received this message in error, please inform the sender immediately by replying to the email and delete this message from your computer. The content of this message and its attachments does not necessarily express the opinion or intention of the company and does not imply any legal obligation or responsibilities for that company. When exchanging messages, you are aware that national and international monitoring and analysis tools are used.
@dinger1986 commented on GitHub (May 19, 2023):
@darouca What so you mean same here?
@darouca commented on GitHub (May 19, 2023):
When I update my system to 0.15.11, the remote control stops working.
I see a 500 error when I open a computer.
Em sex., 19 de mai. de 2023 às 07:48, dinger1986 @.***>
escreveu:
--
CONFIDENCIAL. SUJEITO A PRIVILÉGIO LEGAL DE COMUNICAÇÃO, PROTEGIDO NOS
TERMOS DA LEI. Esta mensagem e seus anexos são endereçados exclusivamente
para seu destinatário e podem conter informações confidenciais ou
privilegiadas e legalmente protegidas, sujeitas a sigilo profissional. Se
você não é o destinatário ou uma pessoa autorizada para recebê-la, você não
deve usar, copiar, divulgar ou tomar qualquer ação com base nesta mensagem
ou quaisquer informações nela contidas. Se você recebeu esta mensagem por
engano, por favor, informe o remetente imediatamente, respondendo o e-mail
e exclua esta mensagem do seu computador. O conteúdo desta mensagem e seus
anexos não necessariamente expressão o parecer ou a intenção da empresa não
implicando qualquer obrigação legal ou responsabilidades. Ao trocar
mensagens, fica ciente que ferramentas, nacionais e internacionais, de
monitoramento e analise são utilizadas.
CONFIDENTIAL. SUBJECT TO LEGAL
PRIVACY OF COMMUNICATION, PROTECTED IN TERMS OF LAW. This message and its
attachments are addressed exclusively to its recipient and may contain
confidential or privileged and legally protected information, subject to
professional secrecy. If you are not the recipient or a person authorized
to receive it, you must not use, copy, disclose or take any action based on
this message or any information contained therein. If you received this
message in error, please inform the sender immediately by replying to the
email and delete this message from your computer. The content of this
message and its attachments does not necessarily express the opinion or
intention of the company and does not imply any legal obligation or
responsibilities for that company. When exchanging messages, you are aware
that national and international monitoring and analysis tools are used.
@wh1te909 commented on GitHub (May 20, 2023):
https://docs.tacticalrmm.com/troubleshooting/#error-500 please paste logs so we can see what the error is...
@silversword411 commented on GitHub (May 20, 2023):
...running your own reverse proxy?
@MAJINFORMATIQUE commented on GitHub (Jun 7, 2023):
Hi, here is details about issue in django;db
column account_user.dash_info_color doesn't exist
@silversword411 commented on GitHub (Jun 7, 2023):
I see the color customization error
@wh1te909 is this from the recent new color stuff?