Thanks for covering me up.
That unfortunately is not how the page should look. It looks very different when I load it internally... im so confused.
Unfortunately that is a Ubuntu/Wordpress issue at this point. It works remotely, in that it successfully reaches your WordPress Website, however there do indeed seem to be issues with your WordPress configuration. I note that it provides "hard-coded" URL's which included links to 10.10.10.xxx/24 addresses which should never be present.
As you want your WordPress site to be accessible access both locally within your 10.10.10.0/24 network, and on your XXX.XX.XX.XX external IP address, you will need your WordPress site to use "relative" URL's rather than "explicit" ones which references to your internal network. (I am an Ubuntu user, but I do not use WordPress at all, so I can not help you with this part of the problem).
Discussion of WordPress would be
off-topic here anyway. Perhaps
Google or some of the WordPress Support resources on the Internet can assist you further. I'm afraid with the pending release of our new Almond+ product, I've haven't had a chance yet to check whether or not our original Almond supports
NAT Loopback properly or not.
If "
NAT Loopback" is supported, then you can probably "hardcode" your Links using your FQDN, rather than your internal 10.10.10.0/24 network address. My Almond is presently setup as an "Access Point" rather than as my "main Router", so I can't easily test this right now. (I will be switching my Network over to my new
Almond+ as my main Router, when it gets here, so I will try to temporarily setup my original Almond as a Router, at that time so that I can test "
NAT Loopback" compatibility for you at that time.
If our Almond product does not support "
NAT Loopback", it will probably require changes to the Firmware to support it properly, but the Almond already has the binaries required to support it, so I'm sure this can be resolved in time if it isn't already supported. Unfortunately very few consumer-grade Routers (from
any manufacturer) support
NAT Loopback correctly, (possibly including our Almond), so this frustrating issue affects a lot of people that want to support "external" access to "internal Websites" hidden behind their
NAT Routers.
Please seek assistance with WordPress using appropriate WordPress resources on the Internet. (Please reply within this message thread if you get it working, and I will investigate our "
NAT Loopback" functionality as soon as I possibly can. Unfortunately I can't easily switch Routers here without affecting other users on my "home" network, so I can not promise to "test" this quickly for you.
I should have my Almond+ Beta product in the coming weeks, so I will be happy to investigate this properly for you at that time.