Skip to Content.
Sympa Menu

geteduroam - Issues using the geteduroam IoS app with self-hosted letswifi service

Subject: An open discussion list for topics related to the geteduroam service

List archive

Chronological Thread  
  • From: "Jamie Getty" <jamie.getty AT reannz.co.nz>
  • To: geteduroam AT lists.geant.org
  • Subject: Issues using the geteduroam IoS app with self-hosted letswifi service
  • Date: Thu, 20 Nov 2025 05:18:40 +0000

Hello, my name is Jamie Getty, from REANNZ. I am working on getting a test
deployment of the letswifi-portal service working with the geteduroam app.
I am in the process of recording everything and reproducing the steps required
to get things up and running, so we have a record for the future.
I have confirmed with the geteduroam.sh shell script that we can request
credentials correctly.
However, when I try connecting with the geteduroam app, it shows me the
following error message:

"Failed to connect

The operation couldn't be completed.
(NSXMLParserErrorDomain error 111.)"

I assume this is because of an issue with the generated XML

So my next step was to capture the output of geteduroam.sh into a file, then
validating that file against the eap-metadata.xsd, and it had a blank line at
the start.
This caused this error:

output.xml:2: parser error : XML declaration allowed only at the start of the
document
<?xml version="1.0" encoding="utf-8"?>

Is this the reason that the geteduroam app is failing to parse our XML?

I also added an extra log to the file www/api/eap-config/index.php to see what
the XML output is, but there was no empty line as the start of the output.
So I suspect this means that somewhere between the index.php script generating
output and our apache2 server returning it, a starting newline is added.

This is a new issue that was a result of me trying to recreate the deployed
letswifi-portal a second time, so I would assume this is an issue with our
deployment.
How should I troubleshoot this?



Archive powered by MHonArc 2.6.24.

Top of Page