Skip to Content.
Sympa Menu

geteduroam - Re: 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

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


Chronological Thread  
  • From: Stefan Paetow <Stefan.Paetow AT jisc.ac.uk>
  • To: "geteduroam AT lists.geant.org" <geteduroam AT lists.geant.org>
  • Subject: Re: Issues using the geteduroam IoS app with self-hosted letswifi service
  • Date: Thu, 20 Nov 2025 12:03:33 +0000
  • Accept-language: en-GB, en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=jisc.ac.uk; dmarc=pass action=none header.from=jisc.ac.uk; dkim=pass header.d=jisc.ac.uk; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=h5oY2AX0Ce5LvQfJM7gM7Z+DuT5sNckT20efoQJGogs=; b=wji3nnuXs3RnEBmlM0bDS09jSME47IVCHHaAq7dbY7sQKFiBLUr5ybJIih9E4M0PejZt3I/06ZNlJ+lmtLyUZx7qAZe5kxr4HW8X+to1cwWoeuvZc7mLwRzhYgyRSANzY4D51gFY0aGbD/OxMXhohTmUo4MxfrJrbCBJLLqCqJxMUpgHPLujMSr5Y9C/Ft64d1/IFECs6GgepTicSw3H4fmNhviBjMQhifRaWjB4/5Bwyw4JJ0BZvHCXaUBlt6OxlgmigDH3sWzJ05G1lieXgYlYYKbHs8OaDZB13YfnTQ8eELzdfWfhIJ3y9j5JPAj5qL5doxmhU4VGcJWdEY/G+g==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=nR/KA0lXu101XALXlxg89jK9JyGIFmO732jdShCIeY3g2R2J6OkbZDAHR2W0CuSeU4t2CG62ySK0dxbIxaJdbb0IO6KNCMX0LgzCXMsUoCSEnrdNt0qP05VWhPP2++KrtgD2N2GF+xfLQnW6hRtMlzBeUdielrgwTDuYdEE5GmIsh14ul+b5Wub/JyzbOiOX+OkZMvG0udlM6rEHurKtLG4KDKNf9summHEWZWxqyq4JM/cJ4pcSyiMZqWyNnDb7nlAVkVyjcEtXHr+AmExx7JP6kjulN6AYOE+jPmXUpHlFXJqe4kW9Gi81hW+lB3PdSSmGjLO20xEgyiiNwHsJHg==
  • Authentication-results: mail.geant.org; dkim=pass (2048-bit key; unprotected) header.d=jisc.ac.uk header.i= AT jisc.ac.uk header.a=rsa-sha256 header.s=selector1 header.b=JO+WUjLr; dkim-atps=neutral
  • Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=jisc.ac.uk;
  • Msip_labels: MSIP_Label_190374fc-c2b5-4c8e-bee8-6305ebc1550a_Enabled=true;MSIP_Label_190374fc-c2b5-4c8e-bee8-6305ebc1550a_Name=External;MSIP_Label_190374fc-c2b5-4c8e-bee8-6305ebc1550a_ActionId=7f240dce-3195-4317-8a52-ae5478a698ff;MSIP_Label_190374fc-c2b5-4c8e-bee8-6305ebc1550a_Tag=50, 0, 1, 1;MSIP_Label_190374fc-c2b5-4c8e-bee8-6305ebc1550a_SetDate=2025-11-20T11:49:42Z;MSIP_Label_190374fc-c2b5-4c8e-bee8-6305ebc1550a_SiteId=48f9394d-8a14-4d27-82a6-f35f12361205;MSIP_Label_190374fc-c2b5-4c8e-bee8-6305ebc1550a_Enabled=true;MSIP_Label_190374fc-c2b5-4c8e-bee8-6305ebc1550a_ContentBits=0;MSIP_Label_190374fc-c2b5-4c8e-bee8-6305ebc1550a_Method=Privileged;

Hi Jamie,

That does indeed sound like that blank line has caused that error, although
that sounds a little... ummm... silly if there's merely whitespace in front
and the parser has a fit about it.

As for debugging, can you connect directly to the (I assume reverse-proxied)
endpoint for the portal and see what happens then? That should definitively
exclude Apache.

Stefan Paetow
Federated Roaming Technical Specialist
eduroam(UK), Jisc

email/teams: stefan.paetow AT jisc.ac.uk
gpg: 0x3FCE5142

For eduroam support, please contact the eduroam team via help AT jisc.ac.uk and
mark it for eduroam’s attention.
I am not available on Mondays and Fridays between 12:00 and 15:00 London time
(UTC in winter, UTC+0100 in summer).

Note: I don’t expect a reply outside of your working hours, since I work
internationally with colleagues in different nationalities with different
religions, customs, and holidays. Reply when it is convenient for you.

Jisc is a registered charity (in England and Wales under charity number
1149740; in Scotland under charity number SC053607) and a company limited by
guarantee registered in England under company number 05747339, VAT number GB
197 0632 86. Jisc's registered office is: 4 Portwall Lane, Bristol, BS1 6NB.
T 0203 697 5800.

Jisc Services Limited is a wholly owned Jisc subsidiary and a company limited
by guarantee which is registered in England under company number 02881024,
VAT number GB 197 0632 86. The registered office is: 4 Portwall Lane,
Bristol, BS1 6NB. T 0203 697 5800.

For more details on how Jisc handles your data see our privacy notice here:
https://www.jisc.ac.uk/website/privacy-notice





On 20/11/2025, 05:18, "geteduroam-request AT lists.geant.org
<mailto:geteduroam-request AT lists.geant.org> on behalf of "Jamie Getty""
<geteduroam-request AT lists.geant.org
<mailto:geteduroam-request AT lists.geant.org> on behalf of
geteduroam AT lists.geant.org <mailto:geteduroam AT lists.geant.org>> wrote:


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.19+.

Top of Page