Conversation

hl3p @harblinger @silverpill what is wrong with my instance first husky stopped working now chanfe doebeit the mitra web works fine

2
0
0
@meso @silverpill @harblinger nexus asbestos was cursed from the start 🥀
0
0
1

@meso @silverpill you got a console error to paste? Since there's no error code it might be CSP, CORS or something like that, maybe routing too, the clanker says chan-fe uses /api/v1/instance and mitra-web uses /api/v2/instance so that's another possibility if your config routes those differently

1
0
1
@harblinger @silverpill @meso it just started happening suddenly it worked fine before this. i havent touched the server in a month
2
0
0
@harblinger @meso @silverpill i also cant get any logs from tail -f /var/log/daemon
2
0
0
@meso @silverpill @meso @harblinger
> i also cant get any logs from tail -f /var/log/daemon

relayd logs are useless, it's just "<IP XYZ> was forwarded to <IP ASDF>" or a failure. For actual debugging, Mitra would need to have its own access logging (sort of how Pleroma does at the "info" log level).
0
0
1

@meso @silverpill @meso i meant from the browser like F12 and seeing what's actually going on when it tries to fetch that /api/v1/instance url

maybe there's an error with a hint in the browser dev console, or under the network tab

0
0
0
@cabanela @silverpill @meso @harblinger (actually had only one downtime incident like a boss)
0
0
0