GitLab Helm Chart Deployed on Minikube - UI 404

I am attempting to deploy gitlab using the helm chart on minikube for evaluation. Minikube is on my local development machine, not in the cloud. I believe I am very close to success. The chart deploys and PODs are created and are stable. However, I am unable to access the gitlab UI.

When I attempt to browse to 192.168.99.100 or 192.168.99.100.nip.io, the response is ‘default back end - 404’ (browsing with firefox at the host machine)

I have followed these two links as closely as possible:

GitLab Helm Chart - (plus comments from the community about minikube)

Developing for Kubernetes with Minikube

The values file is below.

Can someone please help me understand why I am unable to open the gitlab ui?

global:
  ingress:
    configureCertmanager: false
    class: "nginx"
  hosts:
    domain: 192.168.99.100.nip.io
    externalIP: 192.168.99.100
#Don't use certmanager, we'll self-sign
certmanager:
  install: false
#Use the `ingress` addon, not our Ingress (can't map 22/80/443)
nginx-ingress:
  enabled: false
#Save resources, only 2 CPU
prometheus:
  install: false
 GitLab Runner isn't a big fan of self-signed certificates
gitlab-runner:
  install: false
#Reduce replica counts, reducing CPU & memory requirements
gitlab:
  unicorn:
    minReplicas: 1
    maxReplicas: 1
  sidekiq:
    minReplicas: 1
    maxReplicas: 1
  gitlab-shell:
    minReplicas: 1
    maxReplicas: 1
registry:
  minReplicas: 1
  maxReplicas: 1

After updating from the repo, rebuilding from scratch, and then making certain I loaded the self signed cert into my browser, I have successfully accessed the gitlab UI. Now to see if the gitlab system will run.

Try global.ingress.tls.external=true

# values-minikube.yaml
# This example intended as baseline to use Minikube for the deployment of GitLab
# - Services that are not compatible with how Minikube runs are disabled
# - Configured to use 192.168.49.2, and nip.io for the domain

# Minimal settings
global:
  ingress:
    configureCertmanager: false
    class: "nginx"
    tls:
      external: true
  hosts:
    domain: local.com
    externalIP: 192.168.49.2
  shell:
    # Configure the clone link in the UI to include the high-numbered NodePort
    # value from below (`gitlab.gitlab-shell.service.nodePort`)
    port: 32022


# Don't use certmanager, we'll self-sign
certmanager:
  install: false

# Use the `ingress` addon, not our Ingress (can't map 22/80/443)
nginx-ingress:
  enabled: false

# Map gitlab-shell to a high-numbered NodePort cloning over SSH since
# Minikube takes port 22.
gitlab:
  gitlab-shell:
    service:
      type: NodePort
      nodePort: 32022

# Provide gitlab-runner with secret object containing self-signed certificate chain
gitlab-runner:
  certsSecretName: gitlab-wildcard-tls-chain