Skip to main content

The remote connection is established, but only a blank screen is visible instead of the requested page.

It mainly occurs when the user is unable to access the requested page in the rb-app pod. At this time, the page requested by the user is mostlyExternal Network(www.naver.com, www.google.co.kretc.)Since it is highly likely that the rb-app pod runs in the physical equipment and network range ofExternal NetworkYou must first check whether communication is possible with the department.

Expected Cases

It is likely, but it does not necessarily apply to all cases below.

  • Cannot access the requested page (external network) due to webFilter.
  • Unable to access the requested page (external network) due to the firewall.

Inspection Method

  1. Accessing the rb-app pod via ssh
  2. Attempt to download the page requested by the user directly using wget in the rb-app pod Example:wget https://www.naver.com
nobody@dev-kubernetes-worker-10:~$ wget https://www.naver.com
--2025-08-07 05:12:18-- https://www.naver.com/
Resolving www.naver.com (www.naver.com)... 223.130.200.219, 223.130.192.248, 223.130.200.236, ...
Connecting to www.naver.com (www.naver.com)|223.130.200.219|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘index.html’

index.html [ <=> ] 199.91K --.-KB/s in 0.02s

2025-08-07 05:12:18 (8.88 MB/s) - ‘index.html’ saved [204705]

nobody@dev-kubernetes-worker-10:~$
  1. Web FilterIf it is hanging, the certificate will be replaced.사용할 수 없는 인증서(물론 영어로 찍힐 거임)related errors are displayed or업무용 사이트가 아니라 접속 차단되어 응답 대기상태It is likely to wait for a long time.
  2. FirewallIf this is attached, the response is immediate.failthis or응답 대기상태It is highly likely to wait for a long time.
  3. Due to the characteristics of the remote browser product, the rb-app pod must communicate with the external network!