I've got my ssl and forwarding all screwed up...I need guidance

[djjace]

Describe the problem/error/question

I had everything up and running wonderfully. Had about 100 hours in to creating my system. Started working with the ai nodes and needed memory, so I made the decision to install Zep. Part of the install for Zep was to get the load balancers working and configure forwarding. I did as the instructions said, but woke up the next morning to no access via the web interface.
Someone was awesome enough to help me figure out what I did wrong, and I am now able to access via the http, but the https still isn’t working. I moved my domain from my previous hose to Digital Ocean and I set up an ssl with digital ocean

I have tried everything I know, which isn’t much. I have gone thorugh every tutorial and can’t find anything about this.

here is what my main workflow sccreen looks like

2024 02 15 09 57 31 053

my console says this

I am stumped

self hosted on digital ocean docker droplet ubuntu

Information on your n8n setup

• n8n version:
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
• Operating system:

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

• n8n version:
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
• Operating system:

[barn4k]

Hello again @djjace

Some questions regarding the case:

1. Is your SSL certificate issued for the same address, that you are using when trying to connect to the n8n?
2. when you are trying to connect to n8n via HTTPS, do you see any certificate errors in the address bar (like the red https part being crossed or a certificate icon with the red cross)?

[djjace]

So, I got frustrated, backed everything up, started a completely new droplet, followed every single instruction to the letter

new n8n instance is up and running, certificate is issued for the subdomain, and valid

and it’s doing the EXACT same thing as the previous instance. it hangs on the workflows section and where the workflows usually are just does that pulsing thing like it’s loading, and never loads

when I go here: http://n8n.mydomain.com:5678/workflows

it works fine, just tells me it is not secure

[barn4k]

Yes, thats strange. Do the workflows page appeared after you have logged in or they appeared right after you have connected to the n8n?

All I can advice for now is to open a new window in incognito mode, open the dev console (f12), you need the network tab in the console, go to the n8n page. There should be a login page (/credentials), after which you may be able to open workflows (in ordinary way). If something is not opening, check in the network tab for any pages with status 400+, it may be credentials page or workflows. Open the entry with error and try to find what was wrong there

[djjace]

I have to say, I feel like an idiot

Cleared all browser data… Cache, etc and everything works fine

You would think 25 years in online work I would have learned something.,