"Opened as child-window, stopping..."

[slrslr]

Step 1: Please describe your environment

• ZeroNet version: 0.6.5 r3864, Python 2.7.11+, gevent 1.4.0
• Operating system: Ubuntu 16.04 ARM kernel 4.9.160-armada375
• Web browser: FF
• Tor status: available
• Opened port: yes

Step 2: Describe the problem:

Hello, i installed zeronet on this Linux server with public IP
my zeronet.conf:
ui_ip = *
ui_port = 80
i want to use this server as a proxy accessible via its public IP address
during startup it says:
Ui.UiServer Web interface: http://*:80/
Ui.UiServer Added mypubliciphere as allowed host
But any site like ZeroHello, /Config says: "Opened as child-window, stopping..."
I am accessing it via:
http://publicIP/Config
http://publicIP:43110/Config

but the same. I also tried to replace zeronet.conf ui_ip by 127.0.0.1 or public IP, but that not fix this.

Also seen this message:

[17:20:15] Ui.UiServer No user found
[17:20:15] Ui.UiServer Error 403:

curl 127.0.0.1:43110 -L
curl publicip:43110 -L

                <h1>Forbidden</h1>
                <h2>Invalid Accept header to load wrapper</h3>

no other WARN/ERROR log lines in debug.log except "Ui.UiServer Error 403: Invalid Accept header to load wrapper"

UPDATE: in other browser (Chrome) it works and in same browser (Firefox) private browsing window also. In Firefox normal window it continue to not work even when doing clearing cache (Ctrl+F5). Strange is that other zeronet proxy with same revision and setup:
ui_ip = *
ui_port = 80
works ok where this new one do not. (shows "Opened as child-window, stopping)".

UPDATE2: after firefox restart, the page is loading OK

[purplesyringa]

Can this be considered a Firefox bug if it was fixed after Firefox restart? The child window message is most likely because of Firefox handling iframes weirdly, and I'd assume that isn't fixable on ZeroNet side.

@HelloZeroNet Can this be closed?

[HelloZeroNet]

This error is displayed if the window has an opener window defined, because in this case it could be possible that the opener window can read the content or control the window.

I was unable to reproduce the problem, but if this happens often, then we can disable this security feature, as it should not be problem in most of the cases.