Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Not works when using HTTPS reverse proxy #212

Closed
ghost opened this issue Jan 8, 2024 · 3 comments
Closed

Not works when using HTTPS reverse proxy #212

ghost opened this issue Jan 8, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@ghost
Copy link

ghost commented Jan 8, 2024

Current Behavior

It works fine when I am using http://xxxx:5800, but it doesn't work when I use https://xxx:15800. I set the HTTPS reverse proxy as usual.

Expected Behavior

No response

Steps To Reproduce

No response

Environment

  • OS:
  • OS version:
  • CPU:
  • Docker version: d19b48ebd23b
  • Device model:
  • Browser/OS:

Container creation

docker run -d --name firefox -e TZ=Asia/Hong_Kong -e DISPLAY_WIDTH=1920 -e DISPLAY_HEIGHT=1080 -e KEEP_APP_RUNNING=1 -e ENABLE_CJK_FONT=1 -e VNC_PASSWORD=admin -p 5800:5800 -p 5900:5900 -v /root/firefox/config:/config:rw --shm-size 2g jlesage/firefox:latest

Container log

[nginx] starting...
[openbox] starting...
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Could not resolve keysym XF86BrightnessAuto
> Warning:          Could not resolve keysym XF86DisplayOff
> Warning:          Could not resolve keysym XF86Info
> Warning:          Could not resolve keysym XF86AspectRatio
> Warning:          Could not resolve keysym XF86DVD
> Warning:          Could not resolve keysym XF86Audio
> Warning:          Could not resolve keysym XF86ChannelUp
> Warning:          Could not resolve keysym XF86ChannelDown
> Warning:          Could not resolve keysym XF86Break
> Warning:          Could not resolve keysym XF86VideoPhone
> Warning:          Could not resolve keysym XF86ZoomReset
> Warning:          Could not resolve keysym XF86Editor
> Warning:          Could not resolve keysym XF86GraphicsEditor
> Warning:          Could not resolve keysym XF86Presentation
> Warning:          Could not resolve keysym XF86Database
> Warning:          Could not resolve keysym XF86Voicemail
> Warning:          Could not resolve keysym XF86Addressbook
> Warning:          Could not resolve keysym XF86DisplayToggle
> Warning:          Could not resolve keysym XF86SpellCheck
> Warning:          Could not resolve keysym XF86ContextMenu
> Warning:          Could not resolve keysym XF86MediaRepeat
> Warning:          Could not resolve keysym XF8610ChannelsUp
> Warning:          Could not resolve keysym XF8610ChannelsDown
> Warning:          Could not resolve keysym XF86Images
> Warning:          Could not resolve keysym XF86NotificationCenter
> Warning:          Could not resolve keysym XF86PickupPhone
> Warning:          Could not resolve keysym XF86HangupPhone
> Warning:          Could not resolve keysym XF86Fn
> Warning:          Could not resolve keysym XF86Fn_Esc
> Warning:          Could not resolve keysym XF86FnRightShift
> Warning:          Could not resolve keysym XF86Numeric0
> Warning:          Could not resolve keysym XF86Numeric1
> Warning:          Could not resolve keysym XF86Numeric2
> Warning:          Could not resolve keysym XF86Numeric3
> Warning:          Could not resolve keysym XF86Numeric4
> Warning:          Could not resolve keysym XF86Numeric5
> Warning:          Could not resolve keysym XF86Numeric6
> Warning:          Could not resolve keysym XF86Numeric7
> Warning:          Could not resolve keysym XF86Numeric8
> Warning:          Could not resolve keysym XF86Numeric9
> Warning:          Could not resolve keysym XF86NumericStar
> Warning:          Could not resolve keysym XF86NumericPound
> Warning:          Could not resolve keysym XF86NumericA
> Warning:          Could not resolve keysym XF86NumericB
> Warning:          Could not resolve keysym XF86NumericC
> Warning:          Could not resolve keysym XF86NumericD
> Warning:          Could not resolve keysym XF86CameraFocus
> Warning:          Could not resolve keysym XF86WPSButton
> Warning:          Could not resolve keysym XF86CameraZoomIn
> Warning:          Could not resolve keysym XF86CameraZoomOut
> Warning:          Could not resolve keysym XF86CameraUp
> Warning:          Could not resolve keysym XF86CameraDown
> Warning:          Could not resolve keysym XF86CameraLeft
> Warning:          Could not resolve keysym XF86CameraRight
> Warning:          Could not resolve keysym XF86AttendantOn
> Warning:          Could not resolve keysym XF86AttendantOff
> Warning:          Could not resolve keysym XF86AttendantToggle
> Warning:          Could not resolve keysym XF86LightsToggle
> Warning:          Could not resolve keysym XF86ALSToggle
> Warning:          Could not resolve keysym XF86Buttonconfig
> Warning:          Could not resolve keysym XF86Taskmanager
> Warning:          Could not resolve keysym XF86Journal
> Warning:          Could not resolve keysym XF86ControlPanel
> Warning:          Could not resolve keysym XF86AppSelect
> Warning:          Could not resolve keysym XF86Screensaver
> Warning:          Could not resolve keysym XF86VoiceCommand
> Warning:          Could not resolve keysym XF86Assistant
> Warning:          Could not resolve keysym XF86BrightnessMin
> Warning:          Could not resolve keysym XF86BrightnessMax
> Warning:          Could not resolve keysym XF86KbdInputAssistPrev
> Warning:          Could not resolve keysym XF86KbdInputAssistNext
> Warning:          Could not resolve keysym XF86KbdInputAssistPrevgroup
> Warning:          Could not resolve keysym XF86KbdInputAssistNextgroup
> Warning:          Could not resolve keysym XF86KbdInputAssistAccept
> Warning:          Could not resolve keysym XF86KbdInputAssistCancel
> Warning:          Could not resolve keysym XF86RightUp
> Warning:          Could not resolve keysym XF86RightDown
> Warning:          Could not resolve keysym XF86LeftUp
> Warning:          Could not resolve keysym XF86LeftDown
> Warning:          Could not resolve keysym XF86RootMenu
> Warning:          Could not resolve keysym XF86MediaTopMenu
> Warning:          Could not resolve keysym XF86Numeric11
> Warning:          Could not resolve keysym XF86Numeric12
> Warning:          Could not resolve keysym XF86AudioDesc
> Warning:          Could not resolve keysym XF863DMode
> Warning:          Could not resolve keysym XF86NextFavorite
> Warning:          Could not resolve keysym XF86StopRecord
> Warning:          Could not resolve keysym XF86PauseRecord
> Warning:          Could not resolve keysym XF86VOD
> Warning:          Could not resolve keysym XF86Unmute
> Warning:          Could not resolve keysym XF86FastReverse
> Warning:          Could not resolve keysym XF86SlowReverse
> Warning:          Could not resolve keysym XF86Data
> Warning:          Could not resolve keysym XF86OnScreenKeyboard
> Warning:          Could not resolve keysym XF86PrivacyScreenToggle
> Warning:          Could not resolve keysym XF86SelectiveScreenshot
> Warning:          Could not resolve keysym XF86Macro1
> Warning:          Could not resolve keysym XF86Macro2
> Warning:          Could not resolve keysym XF86Macro3
> Warning:          Could not resolve keysym XF86Macro4
> Warning:          Could not resolve keysym XF86Macro5
> Warning:          Could not resolve keysym XF86Macro6
> Warning:          Could not resolve keysym XF86Macro7
> Warning:          Could not resolve keysym XF86Macro8
> Warning:          Could not resolve keysym XF86Macro9
> Warning:          Could not resolve keysym XF86Macro10
> Warning:          Could not resolve keysym XF86Macro11
> Warning:          Could not resolve keysym XF86Macro12
> Warning:          Could not resolve keysym XF86Macro13
> Warning:          Could not resolve keysym XF86Macro14
> Warning:          Could not resolve keysym XF86Macro15
> Warning:          Could not resolve keysym XF86Macro16
> Warning:          Could not resolve keysym XF86Macro17
> Warning:          Could not resolve keysym XF86Macro18
> Warning:          Could not resolve keysym XF86Macro19
> Warning:          Could not resolve keysym XF86Macro20
> Warning:          Could not resolve keysym XF86Macro21
> Warning:          Could not resolve keysym XF86Macro22
> Warning:          Could not resolve keysym XF86Macro23
> Warning:          Could not resolve keysym XF86Macro24
> Warning:          Could not resolve keysym XF86Macro25
> Warning:          Could not resolve keysym XF86Macro26
> Warning:          Could not resolve keysym XF86Macro27
> Warning:          Could not resolve keysym XF86Macro28
> Warning:          Could not resolve keysym XF86Macro29
> Warning:          Could not resolve keysym XF86Macro30
> Warning:          Could not resolve keysym XF86MacroRecordStart
> Warning:          Could not resolve keysym XF86MacroRecordStop
> Warning:          Could not resolve keysym XF86MacroPresetCycle
> Warning:          Could not resolve keysym XF86MacroPreset1
> Warning:          Could not resolve keysym XF86MacroPreset2
> Warning:          Could not resolve keysym XF86MacroPreset3
> Warning:          Could not resolve keysym XF86KbdLcdMenu1
> Warning:          Could not resolve keysym XF86KbdLcdMenu2
> Warning:          Could not resolve keysym XF86KbdLcdMenu3
> Warning:          Could not resolve keysym XF86KbdLcdMenu4
> Warning:          Could not resolve keysym XF86KbdLcdMenu5
Errors from xkbcomp are not fatal to the X server
[services.d] starting statusmonitor...
[services.d] starting x11vnc...
[statusmonitor] starting...
[services.d] starting logmonitor...
[services.d] starting app...
[x11vnc] starting...
[logmonitor] starting...
08/01/2024 09:53:48 passing arg to libvncserver: -rfbport
08/01/2024 09:53:48 passing arg to libvncserver: 5900
08/01/2024 09:53:48 passing arg to libvncserver: -rfbportv6
08/01/2024 09:53:48 passing arg to libvncserver: -1
08/01/2024 09:53:48 passing arg to libvncserver: -httpportv6
08/01/2024 09:53:48 passing arg to libvncserver: -1
08/01/2024 09:53:48 passing arg to libvncserver: -desktop
08/01/2024 09:53:48 passing arg to libvncserver: Firefox
08/01/2024 09:53:48 passing arg to libvncserver: -rfbauth
08/01/2024 09:53:48 passing arg to libvncserver: /root/.vncpass
[app] starting Firefox...
08/01/2024 09:53:48 x11vnc version: 0.9.14 lastmod: 2015-11-14  pid: 852
08/01/2024 09:53:48 Using X display :0
08/01/2024 09:53:48 rootwin: 0x42 reswin: 0x400001 dpy: 0xfecf7040
08/01/2024 09:53:48
08/01/2024 09:53:48 ------------------ USEFUL INFORMATION ------------------
[services.d] done.
08/01/2024 09:53:48 X DAMAGE available on display, using it for polling hints.
08/01/2024 09:53:48   To disable this behavior use: '-noxdamage'
08/01/2024 09:53:48
08/01/2024 09:53:48   Most compositing window managers like 'compiz' or 'beryl'
08/01/2024 09:53:48   cause X DAMAGE to fail, and so you may not see any screen
08/01/2024 09:53:48   updates via VNC.  Either disable 'compiz' (recommended) or
08/01/2024 09:53:48   supply the x11vnc '-noxdamage' command line option.
08/01/2024 09:53:48 X COMPOSITE available on display, using it for window polling.
08/01/2024 09:53:48   To disable this behavior use: '-noxcomposite'
08/01/2024 09:53:48
08/01/2024 09:53:48 Wireframing: -wireframe mode is in effect for window moves.
08/01/2024 09:53:48   If this yields undesired behavior (poor response, painting
08/01/2024 09:53:48   errors, etc) it may be disabled:
08/01/2024 09:53:48    - use '-nowf' to disable wireframing completely.
08/01/2024 09:53:48    - use '-nowcr' to disable the Copy Rectangle after the
08/01/2024 09:53:48      moved window is released in the new position.
08/01/2024 09:53:48   Also see the -help entry for tuning parameters.
08/01/2024 09:53:48   You can press 3 Alt_L's (Left "Alt" key) in a row to
08/01/2024 09:53:48   repaint the screen, also see the -fixscreen option for
08/01/2024 09:53:48   periodic repaints.
08/01/2024 09:53:48 GrabServer control via XTEST.
08/01/2024 09:53:48
08/01/2024 09:53:48 Scroll Detection: -scrollcopyrect mode is in effect to
08/01/2024 09:53:48   use RECORD extension to try to detect scrolling windows
08/01/2024 09:53:48   (induced by either user keystroke or mouse input).
08/01/2024 09:53:48   If this yields undesired behavior (poor response, painting
08/01/2024 09:53:48   errors, etc) it may be disabled via: '-noscr'
08/01/2024 09:53:48   Also see the -help entry for tuning parameters.
08/01/2024 09:53:48   You can press 3 Alt_L's (Left "Alt" key) in a row to
08/01/2024 09:53:48   repaint the screen, also see the -fixscreen option for
08/01/2024 09:53:48   periodic repaints.
08/01/2024 09:53:48
08/01/2024 09:53:48 XKEYBOARD: number of keysyms per keycode 7 is greater
08/01/2024 09:53:48   than 4 and 51 keysyms are mapped above 4.
08/01/2024 09:53:48   Automatically switching to -xkb mode.
08/01/2024 09:53:48   If this makes the key mapping worse you can
08/01/2024 09:53:48   disable it with the "-noxkb" option.
08/01/2024 09:53:48   Also, remember "-remap DEAD" for accenting characters.
08/01/2024 09:53:48
08/01/2024 09:53:48 X FBPM extension not supported.
Xlib:  extension "DPMS" missing on display ":0".
08/01/2024 09:53:48 X display is not capable of DPMS.
08/01/2024 09:53:48 --------------------------------------------------------
08/01/2024 09:53:48
08/01/2024 09:53:48 Default visual ID: 0x21
Mozilla Firefox 94.0
08/01/2024 09:53:48 Read initial data from X display into framebuffer.
08/01/2024 09:53:48 initialize_screen: fb_depth/fb_bpp/fb_Bpl 24/32/7680
08/01/2024 09:53:48
08/01/2024 09:53:48 X display :0 is 32bpp depth=24 true color
08/01/2024 09:53:48
08/01/2024 09:53:48 Listening for VNC connections on TCP port 5900
08/01/2024 09:53:48
08/01/2024 09:53:48 Xinerama is present and active (e.g. multi-head).
08/01/2024 09:53:48 Xinerama: number of sub-screens: 1
08/01/2024 09:53:48 Xinerama: no blackouts needed (only one sub-screen)
08/01/2024 09:53:48
08/01/2024 09:53:48 fb read rate: 1418 MB/sec
08/01/2024 09:53:48 fast read: reset -wait  ms to: 10
08/01/2024 09:53:48 fast read: reset -defer ms to: 10
08/01/2024 09:53:48 The X server says there are 10 mouse buttons.
08/01/2024 09:53:48 screen setup finished.
08/01/2024 09:53:48

The VNC desktop is:      3420bf4230a1:0
PORT=5900

******************************************************************************
Have you tried the x11vnc '-ncache' VNC client-side pixel caching feature yet?

The scheme stores pixel data offscreen on the VNC viewer side for faster
retrieval.  It should work with any VNC viewer.  Try it by running:

    x11vnc -ncache 10 ...

One can also add -ncache_cr for smooth 'copyrect' window motion.
More info: http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching

08/01/2024 09:58:19 Got connection from client 127.0.0.1
08/01/2024 09:58:19   other clients:
08/01/2024 09:58:19 Got 'ws' WebSockets handshake
08/01/2024 09:58:19 Got protocol: binary
08/01/2024 09:58:19   - webSocketsHandshake: using binary/raw encoding
08/01/2024 09:58:19   - WebSockets client version hybi-13
08/01/2024 09:58:19 Disabled X server key autorepeat.
08/01/2024 09:58:19   to force back on run: 'xset r on' (3 times)
08/01/2024 09:58:19 incr accepted_client=1 for 127.0.0.1:41790  sock=10
08/01/2024 09:58:20 created   xdamage object: 0x400040
08/01/2024 09:58:28 created selwin: 0x400041
08/01/2024 09:58:28 called initialize_xfixes()
08/01/2024 09:58:36 cutbuffer_send: no send: uninitialized clients
08/01/2024 09:58:37 Got connection from client 127.0.0.1
08/01/2024 09:58:37   other clients:
08/01/2024 09:58:37      127.0.0.1
08/01/2024 09:58:37 Got 'ws' WebSockets handshake
08/01/2024 09:58:37 Got protocol: binary
08/01/2024 09:58:37   - webSocketsHandshake: using binary/raw encoding
08/01/2024 09:58:37   - WebSockets client version hybi-13
08/01/2024 09:58:37 incr accepted_client=2 for 127.0.0.1:49968  sock=11
08/01/2024 09:58:37 rfbProcessClientProtocolVersion: client gone
08/01/2024 09:58:37 client_count: 1
08/01/2024 09:58:37 Client 127.0.0.1 gone
08/01/2024 09:58:37 Statistics             events    Transmit/ RawEquiv ( saved)
08/01/2024 09:58:37  TOTALS              :      0 |         0/        0 (  0.0%)
08/01/2024 09:58:37 Statistics             events    Received/ RawEquiv ( saved)
08/01/2024 09:58:37  TOTALS              :      0 |         0/        0 (  0.0%)
08/01/2024 09:59:37 rfbProcessClientProtocolVersion: client gone
08/01/2024 09:59:37 client_count: 0
08/01/2024 09:59:37 Restored X server key autorepeat to: 1
08/01/2024 09:59:37 Client 127.0.0.1 gone
08/01/2024 09:59:37 Statistics             events    Transmit/ RawEquiv ( saved)
08/01/2024 09:59:37  TOTALS              :      0 |         0/        0 (  0.0%)
08/01/2024 09:59:37 Statistics             events    Received/ RawEquiv ( saved)
08/01/2024 09:59:37  TOTALS              :      0 |         0/        0 (  0.0%)
08/01/2024 09:59:39 destroyed xdamage object: 0x400040
08/01/2024 10:01:01 Got connection from client 127.0.0.1
08/01/2024 10:01:01   other clients:
08/01/2024 10:01:01 Got 'ws' WebSockets handshake
08/01/2024 10:01:01 Got protocol: binary
08/01/2024 10:01:01   - webSocketsHandshake: using binary/raw encoding
08/01/2024 10:01:01   - WebSockets client version hybi-13
08/01/2024 10:01:01 Disabled X server key autorepeat.
08/01/2024 10:01:01   to force back on run: 'xset r on' (3 times)
08/01/2024 10:01:01 incr accepted_client=3 for 127.0.0.1:42162  sock=10
08/01/2024 10:01:02 created   xdamage object: 0x400042
08/01/2024 10:01:59 rfbProcessClientProtocolVersion: client gone
08/01/2024 10:01:59 client_count: 0
08/01/2024 10:01:59 Restored X server key autorepeat to: 1
08/01/2024 10:01:59 Client 127.0.0.1 gone
08/01/2024 10:01:59 Statistics             events    Transmit/ RawEquiv ( saved)
08/01/2024 10:01:59  TOTALS              :      0 |         0/        0 (  0.0%)
08/01/2024 10:01:59 Statistics             events    Received/ RawEquiv ( saved)
08/01/2024 10:01:59  TOTALS              :      0 |         0/        0 (  0.0%)
08/01/2024 10:02:00 destroyed xdamage object: 0x400042
08/01/2024 10:02:01 Got connection from client 127.0.0.1
08/01/2024 10:02:01   other clients:
08/01/2024 10:02:01 Got 'ws' WebSockets handshake
08/01/2024 10:02:01 Got protocol: binary
08/01/2024 10:02:01   - webSocketsHandshake: using binary/raw encoding
08/01/2024 10:02:01   - WebSockets client version hybi-13
08/01/2024 10:02:01 Disabled X server key autorepeat.
08/01/2024 10:02:01   to force back on run: 'xset r on' (3 times)
08/01/2024 10:02:01 incr accepted_client=4 for 127.0.0.1:37636  sock=10
08/01/2024 10:02:02 created   xdamage object: 0x400043
08/01/2024 10:02:29 Got connection from client 127.0.0.1
08/01/2024 10:02:29   other clients:
08/01/2024 10:02:29      127.0.0.1
08/01/2024 10:02:29 Got 'ws' WebSockets handshake
08/01/2024 10:02:29 Got protocol: binary
08/01/2024 10:02:29   - webSocketsHandshake: using binary/raw encoding
08/01/2024 10:02:29   - WebSockets client version hybi-13
08/01/2024 10:02:29 incr accepted_client=5 for 127.0.0.1:57206  sock=11

Container inspect

No response

Anything else?

1111
@ghost ghost added the bug Something isn't working label Jan 8, 2024
@jlesage
Copy link
Owner

jlesage commented Jan 8, 2024

What doesn't work exactly ? Accessing the container through your reverse proxy ? Note that the container itself is independent from the proxy. If you can access the container successfully without proxy, then the issue is with the proxy configuration. If that the case, you may want to share its configuration to better help you.

@ghost
Copy link
Author

ghost commented Jan 9, 2024

I used Synology reverse proxies. But I think we can close this one. Because it works when I use the way under /config/certs/ to enable HTTPs.

@ghost
Copy link
Author

ghost commented Jan 9, 2024

Closed

@ghost ghost closed this as completed Jan 9, 2024
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jlesage