That's great! Thank you for letting me know.
Just a couple of notes which might help to clarify things (maybe for other users reading this thread)...
... will try moving stuff to eliminate the configUrl
Just for the record, having looked at your code and site, you should have been able to just eliminate the configUrl entry from your embedding code without having to move any files around (as your gallery's configuration file was named 'config.xml and was located directly inside the baseUrl gallery folder).
Looking at the inspector in Firefox helped, the error was "CORS Missing Allow Origin"
Using relative paths is usually the best way to avoid CORS issues.
If you use an absolute path in your embedding code which starts with https:// and includes the www subdomain (for example), then a visitor to your site would have to use https:// and www for the URL in their browser's address bar. If the visitor used http:// or omitted www, then this could trigger a CORS issue. If relative paths are used, such issues can be avoided.
Also, if you were to use absolute paths in your embedding code, then you'd need to ensure that they all use the same protocol (http:// vs https://) and the same domain/subdomain. If there's a mismatch, then the gallery would likely not be displayed, no matter what a visitor might use for the URL in their browser's address bar.
Incidentally, relative paths can either:
(1) be relative to the web page containing the embedding code.
... or:
(2) start with a leading slash which denotes your root directory (and, in doing so, you can build up the relative path starting from the root, rather than the directory that the embedding page is in).
... have a wonderful Christmas.
Thanks! You, too!