Running passbolt on context path

Installation Issues
1

We are running passbolt in EKS env using image: passbolt/passbolt:latest-ce-non-root
our deployment env variable for APP_FULL_BASE_URL = https://someurl/passbolt/

on login, we only see this:

image
image882×287 14.9 KB

How do we fix this ?

Thanks,
Nikesh

2

Hi @nikesh Welcome to the forum!

Have you made sure your server can resolve the domain you are using? Can you ping the domain from the command line?

You may want to provide more info as is requested. About the Installation Issues category

3

yes, we are able to access the domain.

We have created the service for the passbolt and route the request using the istio virtual service:
here is our service yaml: (yes, we have deployed the passbolt on port 8080)

apiVersion: v1
kind: Service
metadata:
name: passbolt
labels:
app: passbolt
spec:
ports:
- port: 8080
targetPort: 8080
selector:
app: passbolt
type: ClusterIP

and here is our istio VS.yaml

  • match:
    • uri:
      prefix: /passbolt/
      route:
    • destination:
      host: passbolt
      port:
      number: 8080
4

Can you provide links to documentation you are working with related to these? What guide(s) are you following?

If it’s not a passbolt documented setup, we can try to follow what you are attempting.

5

Hi @nikesh

APP_FULL_BASE_URL is only for https://someurl. As you are trying to host passbolt on a sub-dirrectory /passbolt, you should define this one with the APP_BASE environment variable:

APP_FULL_BASE_URL=https://someurl
APP_BASE=/passbolt

I got this information from passbolt configuration file

The environment variable for this configuration is defined here.

Let us know if it works for you.

Best,

6

@nikesh Another user had the same scenario here, see example of NGINX settings: Clarify how to use APP_BASE and APP_FULL_BASE_URL · Issue #174 · passbolt/passbolt_docker · GitHub