self-hosted v4.4.6 unable to see any logger event information

[insanity54]

Hi I'm getting started with trigger.dev and I've run into a very annoying problem-- I can't see any logs!

This is a task that successfully ran to completion, but there is no event data, and no logs!

There should be log SPAM, because this is part of the code.

export const audioAnalysisTask = task({
  id: "audio-analysis",
  maxDuration: 360,
  run: async (
    payload: { audioId: string; twitchLogin: string },
    { ctx },
  ) => {
    const { audioId, twitchLogin } = payload;
    const streamSegmentedDuration = ctx.environment.type === 'PRODUCTION' ? '00:05:00' : '00:00:30';
    const baseUrl = process.env.TAILNET_DNS_NAME
      ? `https://${process.env.TAILNET_DNS_NAME}`
      : process.env.PUBLIC_ORIGIN ?? "http://localhost:3000";
    const workerToken = process.env.WORKER_TOKEN;

    console.log(`hello this is a console.log. the baseUrl is`, baseUrl);
    logger.log(`hello this is logger.log and i'll shove some metadata in here.`, { "derp": true });
    logger.info(`hello this is logger.info and I have no metadata`);
    logger.debug('hello this is debug');
    logger.warn('helo this is logger.warn');

But nope, it's all empty, except for that console.log which does show in the terminal, but not in the webUI.

How about the (alpha) logs page?

Only errors and traces. What in the world? Where are the INFO, and LOG levels?

I got the idea to connect to an official trigger.dev cloud instance to see if the problem exists there too. It doesn't! I see logs on official cloud!

I guess this is how it's supposed to look.

I figure there's something wrong with my self-hosted config. The problem? I don't know WHAT. What part? What service? What env var? I have no idea what setting would be causing this.

I dove through logs from the various docker-compose services and I didn't see anything that stuck out.

Any clues as to what could be causing this?

[yudin-s]

For self-hosted Trigger, this usually means the run completed but event/log ingestion is not healthy (UI can show run status while logs/events stay empty).\n\nFast checks in order:\n1. Verify all Trigger services are on the same version (v4.6.6) and healthy (web, worker, and any event/log storage dependencies).\n2. Open browser devtools on the run page and check failing requests for run events/logs (4xx/5xx gives the exact missing component).\n3. Check worker/container env for required storage/queue vars and connectivity (DB/redis/object store depending on your setup).\n4. Trigger a tiny task with only logger.info("hello") and console.log("hello") to see if any log path is working.\n\nYour java.net.SocketException: Network is unreachable in logs is a strong signal that at least one internal fetch path is failing from inside the container network. Fixing that network path usually restores event/log visibility too.\n\nIf you can share one failing request from the run page network tab (URL + status), we can pinpoint the exact component. If this solved it, please mark the answer so others can find it faster.

[insanity54]

Brother you waste my time with your loose cannon AI agent