Project

General

Profile

Actions

Bug #8250

closed

Captive Portal XMLRPC does not use the custom port configured.

Added by Louis Casambre over 6 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Captive Portal
Target version:
-
Start date:
12/31/2017
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.4.2_1
Affected Architecture:

Description

WebGUI is configured to use https through port 8080. However when synchronizing changes to the captive portal the following message is found in the system log: rc.prunecaptiveportal: New alert found: A communications error occurred while attempting to call XMLRPC method exec_php: Unable to connect to tls://192.168.1.251:443. Error: Operation timed out.

Actions #1

Updated by Louis Casambre over 6 years ago

  • it is not a bug **
Actions #2

Updated by A FL over 5 years ago

I could not reproduce this. XMLRPC is working fine on a custom port (using sync settings in captiveportal->Vouchers menu)

This can be closed.

Also, a new feature has been induced when fixing #7972 : HA Sync can now use server defined in General -> high Availability Sync.

"high Availability Sync" Page does not provide any option to set a custom port. I know this is a separate issue, but settting a custom port for peer could be a nice feature?

Actions #3

Updated by Jim Pingle over 5 years ago

  • Status changed from New to Closed

The ports have to be the same on the GUI for both units. Leaving out the port number is intentional.

Actions

Also available in: Atom PDF