Dump1090-mutability not working over wifi

I have had my raspberry pi up and running for a couple of months but now want relocate it to get a better antenna position. For this will need to use wifi rather than the ethernet cable I have at present. The wifi dongle is working and connected to my router. With the cable and wifi dongle connected I am able get use the address below to get map with data overlayed.

192.168.0.14/dump1090/gmap.html
192.168.0.12/dump1090/gmap.html

192.168.0.14 is my wifi dongle IP and 192.168.0.12 is the cable IP.

When I disconnect the cable I get the error Ajax call failed (Timeout:Timeout) when I try 192.168.0.14/dump1090/gmap.html.

Ifconfig details are below.

eth0 Link encap:Ethernet HWaddr b8:27:eb:b3:98:12
inet addr:192.168.0.12 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::42da:2c18:9189:24d8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2612714 errors:0 dropped:472 overruns:0 frame:0
TX packets:3312125 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:358064757 (341.4 MiB) TX bytes:643986312 (614.1 MiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:14576181 errors:0 dropped:0 overruns:0 frame:0
TX packets:14576181 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:3868178260 (3.6 GiB) TX bytes:3868178260 (3.6 GiB)

wlan0 Link encap:Ethernet HWaddr 00:11:50:bd:3a:e9
inet addr:192.168.0.14 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::211:50ff:febd:3ae9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:822904 errors:0 dropped:0 overruns:0 frame:0
TX packets:250235 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:71270965 (67.9 MiB) TX bytes:29852547 (28.4 MiB)

Any help would be appreciated.

Are you using a piaware 3 sdcard image or did you set it up yourself?

If you set it up yourself be aware that you will need to set different metrics on the two sets of routes or they tend to clobber each other unpredictably when the interface state changes (e.g. when disconnecting a cable). You might want to try rebooting with the wired network disconnected and see if that comes up OK.

Thanks obj restarting the RP solved the problem.