Why the cloud portal authentication page cannot be displayed or Is loaded slowly only on an iOS Terminal?

You can try the following steps to troubleshoot this issue.

• Check whether the portal authentication configuration is correct
  

Ruijie AP cloud portal authentication configuration example:

!   http redirect port 443   web-auth acct-update-interval 1    web-auth sta-perception enable    web-auth sta-preemption enable   !    web-auth template wifidog_1 wifidog    ip 35.190.54.251    nas-ip 1.2.3.4    url  http://portal.ruijienetworks.com/auth/wifidogAuth    redirect js    !   wlansec 1    web-auth portal wifidog_1    webauth   !

• Check whether the authenticated user can connect to the network and obtain an IP address successfully
  
  

Before portal authentication, the client needs to obtain an IP address. If the client does not obtain an IP address, check whether the DHCP server and VLAN configurations between the DHCP server and client are correct.

• Check the network between the client and the portal server
  
  

If the user fails to access the portal server, check the network or portal server. You can run telnet +portal domain name 80 command to check further check the network connectivity with the portal server. If the port is reachable, can page can be redirected normally.

• Check whether the DNS server resolves the portal domain name successfully.
  
  

DNS resolution issues can prevent the client from generating HTTP/HTTPS traffic, leading to a failure in triggering redirection.You can use ping to test the domain and check if it resolves to an IP address, or capture packets on the client (PC) to analyze whether the DNS responses for the domain requests are correct. If the resolution is abnormal, check the connectivity between the client and the DNS server.

• Try to manually enter an IP address like 4.4.4.4 to see if the authentication page appears. If it does, the portal page pop-up may be blocked by the client. In this case, you can try to replace the client and test whether all the terminal devices have the same issue.
  
  

For example, the iOS terminal accesses captive.apple.com for connectivity verification. In normal cases, portal redirection is triggered to push the authentication page only after the connectivity verification succeeds. If it takes quite a long time for the DNS server to resolve the domain name, the speed at which the authentication page is loaded is also affected.

• Capture the packets on the uplink device to further check whether the authentication device can identify the client HTTP and HTTPs traffic to trigger the redirection normally.
  
  

If the traffic from the terminal is HTTPS and no HTTPS redirection is configured. To trigger redirection for HTTPS traffic, run the following command:

http redirect port 443

If the above solutions can't solve your problems,please contact
Ruijie TAC support
for help.