Wordpress , newest version OC and firmware 16.1 release date

[Jocko]

Hi raidsm,

I then wanted to test today via WAN (at my job) but as I forwarded a non standard port (8080 instead of 80 to avoid some web indexing) this is also not working. The NAS webpage is working fine (ie: ns2.net:8080) but the wordpress site (ns2.net:8080/www) is not working? Unable to reach because of a time out... Maybe I should use forward the standard port for a reason , I don't understand that either...

:thinking apache server uses by default the ports 80 (http) and 443 (https). You can not change the port 80 but only for https. So I assume that you did it for https protocol (?). In this case, the url is https://ns2.net:8080/...
Yes you need to forward the port 8080 (or 80 or 443) to redirect sockets received by your router on its public IP (WAN) toward the local IP of your NAS. So make rule for TCP protocol with the port used.
For using https protocol, your need to have a valid certificate (CN=ns2.net)

!	Be careful, many router do not like and do not support "loopback" (https://www.google.com/search?q=router+loopback&ie=utf-8&oe=utf-8) so you can not use your DDNS from a local host. Then for example, use a smartphone to test with a direct Internet access (provided by your ISP and not via your wifi)

With OS X, I think you need to add the domain '.local' for resolving the nas hostname. (Then Bonjour will be able to resolve it).
Otherwise by editing manually the file etc/hosts (1 line by hosts with the syntax 'ip(space)hostname' will work also.
Currently, the local name of the NAS is known via netbios by the other hosts.
So it is why the hostname is always resolved by your Win7 / 10
Then try

Code: Select all

ping nasname.local

[raidsm]

Hi jocko ,

what I did is port forward on my router.

WAN TCP port 8080 to LAN TCP port 80
WAN TCR port 8080 to LAN TCR port 443

I did use my cell phone (on cell coverage) to try as I know some router doesn't like loopback as you told. In fact airport extreme do like it and normaly works great. (tested with the nas homepage) I also try at work. Both dosn't work.
BUT the fvdw main page of my router do work (http://ns2.net:8080 or https://ns2.net:8081. Only the wordpress do not work. webpage seems to be unreacheble (http://ns2.net:8080/www) It says server time out... Is it something Apache dosn't like? I will revert to standard port tonight just to make sure.

I also tried to ping the host ns2.local without success. What is weird is my windows VM (hosted by my MAC) is also unable to ping the host! Maybe it's related to the way VMware fusion handle the network interface. I did try other NIC method in vmware to isolate both NIC without success...)

This is still intriguing me that on windows my wordpress page show up and not on my MAC. There is something the way URL are handled localy (and maybe on the WAN side I couln't test right now) It's unfortune as I cant use it that way!. :hairpull

I don't want to edit the host file as it's a problem that every one that have a mac won't be able to access my website...

ow god.. :hammerhead

[Jocko]

WAN TCP port 8080 to LAN TCP port 80
WAN TCR port 8080 to LAN TCR port 443

I assume you wanted to write

Code: Select all

WAN TCP port 8080 to LAN TCP port 80
WAN TCR port 8081 to LAN TCR port 443

;)

BUT the fvdw main page of my router do work (http://ns2.net:8080 or https://ns2.net:8081. Only the wordpress do not work. webpage seems to be unreacheble (http://ns2.net:8080/www)

That means you use a wrong url.
Do you still have a symlink www in /usr/htdocs ? and updated ?

Afp server is it running ? (as in the same time a Bonjour service is started)

I don't want to edit the host file as it's a problem that every one that have a mac won't be able to access my website...

This trick must be used only for local hosts. So I assume not many..
For remote hosts, it will use your ddns to get your public IP and then the router will use the local ip of your nas via your Nat rules

[raidsm]

Exactly I wanted to write https port 8081 My bad! ;)

My symlinks is still there , working fine as it's working great on my native windows laptop.

Do I need to update it?

Yes AFP is running.

I will try to edit my host file on my mac tonight. I will also try with default ports forward on my router. What drive me nuts is why it's working properly on my windows laptop and not on my mac (localy)

[Jocko]

Maybe there is an issue with your symlink (see one symlink www in htdocs and also one in htdocs/www)

Do in putty

Code: Select all

ls -l /usr/htdocs/www

(then you should be able to see its target and so valid it. It should be ok as you wrote it)
To look at what it is the 2d symlink do

Code: Select all

ls -l /usr/htdocs/www/www

and to remove it safely do

Code: Select all

unlink /usr/htdocs/www/www

But this does not explain your Mac issue.

Do you try with a slash at the end of the url (http://ns2.net:8080/www/) and also with index.php (http://ns2.net:8080/www/index.php) maybe safari does not have the same behaviour as the browser used on M$ (I don't like safari).

[raidsm]

well I was able to remotely configure my router tu use standard ports. I am now able to access my wordpress website from work but I got the same result as I got with localy with my mac

here is a picture attached.

I also removed the uneccesary symlink I made by mistake.

This is sooo strange. What does changing nat port mapping has to do with being able to access a website IF you type the adresse with including the port number correctly? Is it a appache problem? From now I will use default port but as i'm curions...

I don't think it's a mac only problem I think it's a host resolving issue... Maybe it's a Mysql or a database connectivity issue?

[raidsm]

Do you try with a slash at the end of the url (http://ns2.net:8080/www/) and also with index.php (http://ns2.net:8080/www/index.php) maybe safari does not have the same behaviour as the browser used on M$ (I don't like safari).[/quote]

I have the same problem at my job with a windows computer

I did try to reach at http://ns2/www/index.php but got the same result as typing ns2/www. So redirection to index fonction properly.

Just a note , ns2/www is not the real link to my website...

Next step , I think I will scrap all my wordpress configuration and start the install (run the wp-admin/install.php script) from a remote location (ie at my job). Maybe in the installation process there is some link made that are false because I did it localy? Do that make any sense at all? Maybe there is some hardcode inserted...

I'm not a fan of trying anythig but I do not understand all of what is going on! :hairpull

[Jocko]

This is sooo strange. What does changing nat port mapping has to do with being able to access a website IF you type the adresse with including the port number correctly? Is it a appache problem? From now I will use default port but as i'm curions...

No. I use not standard port (https) for my nas without issue.
But I note that you crossed ports in/out with not standard port with standard port
Often router opens silently its firewall for the usual ports so maybe you should look at your firewall rules and copy them for your custom http/https nat rules

To check your router settings, just add a file index.html in www with this content

Code: Select all

<html><body>coucou</body></html>

If you can get it everywhere with the url http(s)://ns2.net:yourport/www/index.html then the router settings are ok
And if you still have an issue with wordpress page then you need to deepen on this side.

[raidsm]

Hi Jocko,

good news tonight! after testing everything I could and as nothing was working properly , I did a last install of another wordpress but this time from my mac on my home network (instead of a work windows 7 laptop plugged directly to the gas via ethernet even without a switch in-between...)

I don't know why but EVERYTHING is working fine! :rock

I just did another new database , another symlink , another share , edit my .htaccess and pick up a new wordpress package et VOILA. Everything is working as it should. Wow , seems easy now but it's not that simple when you don't know noting (almost) in unix. It was really fun and with your help it's now working properly! :bananadance

If you think someone would be interested I could make a small topic resuming each step? :thumbup

Maybe this package (wordpress) will be built in a future release of fvdw? ;)- :shocked

[Jocko]

:thumbup

Maybe this package (wordpress) will be built in a future release of fvdw?

In fvdw-sl image no but maybe we go to build an add-on package like pyload or plex.