CSFR error

Can you share more details about your setup and what command you used to start WebODM?

Webodm running on a docker container. I have tried the simple ./webodm.sh start but typically we use. ./webodm.sh --default-nodes 1 start --ssl --hostname xxxx.xxxx.com --ssl-key ./key.pem --ssl-cert ./full.pem

Mm, strange; did you make any changes to WebODM's code or is this a vanilla WebODM?

I've made no changes. I did a total rebuild last night, and today I can access it over HTTP after clearing cookies. As soon as I enable SSL, the error comes back. Tried clearing cookies again, but it does not work unless I change back to HTTP.

are you accessing WebODM via https://xxxx.xxxx.com ?

yes

does it work if you access it from an Incognito browser tab?

no same result

can you share the actual URL ?

http://webodm.jp2g.com:8000 is what's currently working

I can trun on SSL again if you would like?

turn

one sec

https://webodm.jp2g.com:8000

I see this on the docker screen also

Open port 443 on the firewall, then try to access: https://webodm.jp2g.com

it is

so drop the 8000?

so you would like me to use the --port attribute and set it to 443?

no need; when --ssl is enabled, it defaults to 443

so don't specify a port (omit --port)

ok but why do I see this?

here's another snip after running the command I use

port 8000 is used internally (inside docker), but should map to 443 --> 8000 once everything is running. Open port 443, it should work then.

Ok I can confirm 443 is open…

Other things to try; let letsencrypt generate the SSL certificate instead of providing your own key/pem (drop --ssl-cert and -ssl-key). If it loads then, it's an issue with the certificate

If that still doesn't work, I'm out of ideas

k thank you

got this

it did change to 443 though

but not accessible

Wonder if 8443 would open. Stab at 8080 typical non windows servers and 8443 the ssl flavor.
WebODM at the front might pass to and through 8000

ok I think I got it to work. I messed around trying to get Let's Encrypt to work, and it does not play well with FortiGate firewalls. Beat my head a bunch more times. I ended up adding the --port 443 in my command line to start WebODM as a long shot, but it WORKED!! Thank you, guys, for your help!