The commands I provided install wordpress without any supporting SME scripts or other commands -- so there won't be any "event" with wordpress in the name of the event (no "signal-event wordpress-update").
To update firewall and httpd configurations after making changes use
signal-event remoteaccess-update
Unless you've done something you haven't mentioned yet, there shouldn't be anything in the "config" database for wordpress -- everything we did was in the "accounts" and "domains" databases. The commands I gave for creating the ibay had public access enabled:
# create ibay
IBAY=wordpress
/sbin/e-smith/db accounts set $IBAY ibay FollowSymLinks enabled CgiBin enabled AllowOverride All Group www PublicAccess global UserAccess wr-group-rd-everyone PhpVersion php71
/sbin/e-smith/signal-event ibay-create wordpress
The "config" setting that would affect public access to your new ibay (to the server in general) is for the "httpd-e-smith" service. Make sure that "httpd-e-smith" has "access=public":
# config show httpd-e-smith
httpd-e-smith=service
SSLv2=disabled
SSLv3=disabled
TCPPort=80
access=public
status=enabled
Is your dyndns domain name the same as your primary domain name? The commands provided configure Apache to serve wordpress using the primary domain name -- if you really need it to appear at a different domain you need to create that new domain and tell the server to use the wordpress ibay for content.
You can get the default domain using
config get DomainName
Finally, the first time you browse to wordpress and let it run its install script, it sets database values based on the URL you used -- if you didn't use the same *public* address during setup, you'll need to correct them before wordpress will work. Wordpress itself (nothing specific to SME) redirects visitors to the specified address before serving any content.
To check and change the wordpress address, login to wordpress "wp-admin", navigate to "Settings" and make sure the "Wordpress Address" and "Site URL" use the correct, public address (you need to be able to access your wordpress using the same URL from both inside and outside your network).
* If they are NOT correct, change them BOTH to the correct value.
* If the correct value only works publicly, you will lose local access to the site
* If things get messed up, you can set these values manually in wp-config.php as described here:
https://codex.wordpress.org/Changing_The_Site_URLWhile testing this for you I changed only the "Site Address (URL)" to my LAN IP address to see what would happen. This prevented me from logging in. I set both values in wp-config.php, logged in and found the two fields greyed out in wp-admin - removed the lines from wp-config.php, refreshed the page, and was able to reset them to the correct value...