Helm Applications Not Working | K8s not Properly Set Up?

I have a bare metal setup with MetalLB and nfs-subdir via helm (source). I am using k8s v1.20.5 with one master and two worker nodes. I installed JupyterHub with Helm, setting the secretkey and readjusted the allocated volume. On run, the pods look fine but when I use the external-ip to run JupyterHub the page keeps loading infinitely. When I use helm to deploy nginx server, it works perfectly fine (so I believe MetalLB works) . But when I am trying to deploy JupyterHub or rather even a Worpress server as a matter of fact. They do not load.
The logs of the wordpress pods are given below

kubectl logs wordpress-mariadb-0 
mariadb 16:13:17.61 
mariadb 16:13:17.61 Welcome to the Bitnami mariadb container
mariadb 16:13:17.61 Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-mariadb
mariadb 16:13:17.62 Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-mariadb/issues
mariadb 16:13:17.62 
mariadb 16:13:17.62 INFO  ==> ** Starting MariaDB setup **
mariadb 16:13:17.64 INFO  ==> Validating settings in MYSQL_*/MARIADB_* env vars
mariadb 16:13:17.64 INFO  ==> Initializing mariadb database
mariadb 16:13:17.66 WARN  ==> The mariadb configuration file '/opt/bitnami/mariadb/conf/my.cnf' is not writable. Configurations based on environment variables will not be applied for this file.
mariadb 16:13:17.66 INFO  ==> Using persisted data
mariadb 16:13:17.68 INFO  ==> Running mysql_upgrade
mariadb 16:13:17.69 INFO  ==> Starting mariadb in background
mariadb 16:13:19.73 INFO  ==> Stopping mariadb
root@master:~# kubectl logs wordpress-795ffdb6c-8jqps
wordpress 16:13:04.35 
wordpress 16:13:04.35 Welcome to the Bitnami wordpress container
wordpress 16:13:04.35 Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-wordpress
wordpress 16:13:04.36 Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-wordpress/issues
wordpress 16:13:04.36 
wordpress 16:13:04.36 INFO  ==> ** Starting WordPress setup **
realpath: /bitnami/apache/conf: No such file or directory
wordpress 16:13:04.39 INFO  ==> Configuring the HTTP port
wordpress 16:13:04.40 INFO  ==> Configuring the HTTPS port
wordpress 16:13:04.42 INFO  ==> Configuring PHP options
wordpress 16:13:04.43 INFO  ==> Validating settings in MYSQL_CLIENT_* env vars
wordpress 16:13:04.49 WARN  ==> You set the environment variable ALLOW_EMPTY_PASSWORD=yes. For safety reasons, do not use this flag in a production environment.
wordpress 16:13:04.59 INFO  ==> Ensuring WordPress directories exist
wordpress 16:13:04.59 INFO  ==> Trying to connect to the database server

I can’t figure out whether the problem exists with my pvc or metalLB. Would really appreciate any help. Thank you!!

Cluster information:

Kubernetes version:1.20.5
Cloud being used: bare-metal
Host OS: Ubuntu 20.04