Akash ingress returns 404 with `cname`'d domain

I’ve attached my deployment’s ingress URI to a subdomain via a CNAME record, however when I visit said domain, I get a 404 page from nginx. Directly visiting the ingress URI works just fine, so the following record

target.domain.tld 260 IN CNAME ingress-uri.ingress.mainnet.akashian.io.

should also work just fine, unless maybe i’ve missed something…

EDIT: i missed something… forgot to enable my domain in the deployment manifest… thanks to @abozanich for pointing that out! (for some reason I don’t see a mark as solution button, so i’m adding this here)

manifest/deploy.yml:

version: "2.0"

services:
  app:
    image: my-awesome-image
    env:
      - NPM_CONFIG_PRODUCTION=true
      - PEERS=peers
    expose:
      - port: 8765
        as: 80
        to:
          - global: true

profiles:
  compute:
    app:
      resources:
        cpu: 
          units: 1
        memory: 
          size: "2Gi"
        storage: 
          size: "2Gi"
  placement:
    westcoast:
      attributes:
        datacenter: equinix-metal-sjc1
      signedBy:
       anyOf:
        - "akash1365yvmc4s7awdyj3n2sav7xfx76adc6dnmlx63"
      pricing:
        app: 
          denom: uakt
          amount: 10

deployment:
  app:
    westcoast:
      profile: app
      count: 1

Hi @its.maddie, can you paste your (anonymized) deploy.yaml in a code block?

The following would help as well:

  • account address
  • deployment sequence

I don’t see anything attached; maybe I’m just missing it?

1 Like

sorry!!! i’ve edited the original post with that info

Great, thanks!

You need to add your CNAME host to the accept list. See the example here.

After you edit your deploy.yaml, you’ll want to:

  1. Update the on-chain version of your deployment with akash tx deployment update.
  2. Send the updated manifest to the provider akash provider send-manifest.

Hopefully that will get you going.

2 Likes

:woman_facepalming: how did i overlook that, thanks for your help and sorry for the bother!

2 Likes