I use Online Banking with HSBC on an almost daily basis, using Mozilla Firebird on Ubuntu.
Since Saturday, I only get an error message when I try to go to the
Sign-up page:
503 ERROR
The request could not be satisfied.
The Lambda function associated with the CloudFront distribution is
invalid or doesn't have the required permissions. We can't connect to
the server for this app or website at this time. There might be too
much traffic or a configuration error. Try again later, or contact the
app or website owner. If you provide content to customers through
CloudFront, you can find steps to troubleshoot and help prevent this
error by reviewing the CloudFront documentation.
I have researched this, and I have no idea what is usually discussed,
it is in a language level above my pay grade, but seems to say that it
is probably a problem with CloudFront, whoever they are.
If I use Chrome, still on Ubuntu, it works fine. That is always
updating whenever I do an update/upgrade.
What, if anything, can I do about this, apart from trying to contact
HSBC's annoying chatbot and explaining it to them? There have been no
recent updates to Mozilla, and there are none ready to download.
Am 24.09.2023 um 09:13:06 Uhr schrieb Davey:
I use Online Banking with HSBC on an almost daily basis, using
Mozilla Firebird on Ubuntu.
Mozilla Firebird?
Really?
Or Firefox?
Since Saturday, I only get an error message when I try to go to the
Sign-up page:
503 ERROR
The request could not be satisfied.
The Lambda function associated with the CloudFront distribution is
invalid or doesn't have the required permissions. We can't connect
to the server for this app or website at this time. There might be
too much traffic or a configuration error. Try again later, or
contact the app or website owner. If you provide content to
customers through CloudFront, you can find steps to troubleshoot
and help prevent this error by reviewing the CloudFront
documentation.
I have researched this, and I have no idea what is usually
discussed, it is in a language level above my pay grade, but seems
to say that it is probably a problem with CloudFront, whoever they
are. If I use Chrome, still on Ubuntu, it works fine. That is always updating whenever I do an update/upgrade.
Many webmasters only care about Chrome.
Contact them and ask them for supporting all browsers.
What, if anything, can I do about this, apart from trying to contact
HSBC's annoying chatbot and explaining it to them? There have been
no recent updates to Mozilla, and there are none ready to
download.
Switching the bank is the last resort.
Am 24.09.2023 um 09:13:06 Uhr schrieb Davey:
I use Online Banking with HSBC on an almost daily basis, using
Mozilla Firebird on Ubuntu.
Mozilla Firebird?
Really?
Or Firefox?
Since Saturday, I only get an error message when I try to go to the
Sign-up page:
503 ERROR
The request could not be satisfied.
The Lambda function associated with the CloudFront distribution is
invalid or doesn't have the required permissions. We can't connect
to the server for this app or website at this time. There might be
too much traffic or a configuration error. Try again later, or
contact the app or website owner. If you provide content to
customers through CloudFront, you can find steps to troubleshoot
and help prevent this error by reviewing the CloudFront
documentation.
I have researched this, and I have no idea what is usually
discussed, it is in a language level above my pay grade, but seems
to say that it is probably a problem with CloudFront, whoever they
are. If I use Chrome, still on Ubuntu, it works fine. That is always updating whenever I do an update/upgrade.
Many webmasters only care about Chrome.
Contact them and ask them for supporting all browsers.
What, if anything, can I do about this, apart from trying to contact
HSBC's annoying chatbot and explaining it to them? There have been
no recent updates to Mozilla, and there are none ready to
download.
Switching the bank is the last resort.
I managed to talk to a human (!), but she could find no reference to
anybody else with similar problems reported. She suggested I do a
Browser Reset.
Am 24.09.2023 um 11:10:23 Uhr schrieb Davey:
I managed to talk to a human (!), but she could find no reference to anybody else with similar problems reported. She suggested I do a
Browser Reset.
Did you try it in a fresh firefox profile?
Go to about:profiles to create it.
Marco Moock wrote:
Did you try it in a fresh firefox profile?
Go to about:profiles to create it.
Ah-ha! That worked. Which proves something, I just don't know how to
fix it.
Davey wrote:
Marco Moock wrote:
Did you try it in a fresh firefox profile?
Go to about:profiles to create it.
Ah-ha! That worked. Which proves something, I just don't know how to
fix it.
start by clearing cookies and/or saved credentials for the bank, then
try disabling all add-ons, then just disable advert/javascript
blocking add-ons...
I thought that the troubleshooting mode had disabled the add-ons etc,
but I'll go through the whole process. Later, though, I have other
things to do at the moment.
Davey wrote:
I thought that the troubleshooting mode had disabled the add-ons
etc,
yes within the fresh profile, but presumably you want to get back to
your original profile?
but I'll go through the whole process. Later, though, I have other
things to do at the moment.
I managed to talk to a human (!), but she could find no
reference to anybody else with similar problems reported.
Davey:
I managed to talk to a human (!), but she could find no
reference to anybody else with similar problems reported.
It may be the standard manipulation: to tell everyone in
private that they are the only one experiencing the problem.
This is why commerical providers do not use public issue
trackers or support forums (mailing lists, newsgroups), to
keep the clients isolated as it were in one-man
cells -- divide and conquer. That way, the client cannot
unite to exert any serious and concerted pressure on the
provider.
It may be the standard manipulation: to tell everyone in
private that they are the only one experiencing the problem.
This is why commerical providers do not use public issue
trackers or support forums (mailing lists, newsgroups), to
keep the clients isolated as it were in one-man
cells -- divide and conquer. That way, the client cannot
unite to exert any serious and concerted pressure on the
provider.
It may be the standard manipulation: to tell everyone in
private that they are the only one experiencing the
problem.
I agree; but the fact that I can get it to work with a new
profile rather negates that IN THIS CASE.
It may be the standard manipulation: to tell everyone in
private that they are the only one experiencing the problem.
This is why commerical providers do not use public issue
trackers or support forums (mailing lists, newsgroups), to
keep the clients isolated as it were in one-man
cells -- divide and conquer. That way, the client cannot
unite to exert any serious and concerted pressure on the
provider.
Anton Shepelev wrote:
It may be the standard manipulation: to tell everyone in
private that they are the only one experiencing the problem.
This is why commerical providers do not use public issue
trackers or support forums (mailing lists, newsgroups), to
keep the clients isolated as it were in one-man
cells -- divide and conquer. That way, the client cannot
unite to exert any serious and concerted pressure on the
provider.
Except they all seem to use twitter!
On Mon, 25 Sep 2023 10:49:36 +0300 Anton Shepelev <anton.txt@g{oogle}mail.com> wrote:
Davey:I agree; but the fact that I can get it to work with a new profile
I managed to talk to a human (!), but she could find no reference to
anybody else with similar problems reported.
It may be the standard manipulation: to tell everyone in private that
they are the only one experiencing the problem.
This is why commerical providers do not use public issue trackers or
support forums (mailing lists, newsgroups), to keep the clients
isolated as it were in one-man cells -- divide and conquer. That way,
the client cannot unite to exert any serious and concerted pressure on
the provider.
rather negates that IN THIS CASE.
But then, Chrome failed this morning, with the same Error message, using
the same profile as yesterday, so who knows?
Cheers,
Have you got Wireshark installed? Using it to look at the traffic between Chrome and your bank might suggest fixes.
Martin Gregorie wrote:
Have you got Wireshark installed? Using it to look at the traffic between Chrome and your bank might suggest fixes.
You would hope communication to the bank would encrypted, which somewhat complicates the process of deciphering https sessions with wireshark
Andy Burns <usenet@andyburns.uk> wrote:
Martin Gregorie wrote:
Have you got Wireshark installed? Using it to look at the traffic
between Chrome and your bank might suggest fixes.
You would hope communication to the bank would encrypted, which
somewhat complicates the process of deciphering https sessions with wireshark
You can use your browser's Developer Tools to see the communication
between the browser and the site inside the HTTPS. But good luck
hunting for fixes: 'stuff talks to stuff' is as good as you'll get
really - there is too many layers of Javascript in there to easily
determine the problem, unless it's something very obvious like a
webserver taking forever to reply. It's a bit like trying to debug
Microsoft Office using a disassembler.
Theo
Martin Gregorie wrote:
Have you got Wireshark installed? Using it to look at the traffic
between Chrome and your bank might suggest fixes.
You would hope communication to the bank would encrypted, which somewhat complicates the process of deciphering https sessions with wireshark
On 25 Sep 2023 16:28:01 +0100 (BST)
Theo <theom+news@chiark.greenend.org.uk> wrote:
Andy Burns <usenet@andyburns.uk> wrote:
Martin Gregorie wrote:
Have you got Wireshark installed? Using it to look at the traffic
between Chrome and your bank might suggest fixes.
You would hope communication to the bank would encrypted, which
somewhat complicates the process of deciphering https sessions with
wireshark
You can use your browser's Developer Tools to see the communication
between the browser and the site inside the HTTPS. But good luck
hunting for fixes: 'stuff talks to stuff' is as good as you'll get
really - there is too many layers of Javascript in there to easily
determine the problem, unless it's something very obvious like a
webserver taking forever to reply. It's a bit like trying to debug
Microsoft Office using a disassembler.
Theo
And all that the three of you have suggested sounds to be beyond my abilities.
But thank you for the ideas!.
On Mon, 25 Sep 2023 14:56:32 +0100, Andy Burns wrote:
Martin Gregorie wrote:
Have you got Wireshark installed? Using it to look at the traffic
between Chrome and your bank might suggest fixes.
You would hope communication to the bank would encrypted, which somewhat complicates the process of deciphering https sessions with wireshark
Agreed, though the earlier parts of the login dialogue, which seem to be where the OP's problems lie, may be plaintext: after you need to have some sort of link up and running before you can turn encryption on. If this initial part of starting an encrypted link is where the OP's problem lies then I'd expect Wireshark could be quite useful.
Martin Gregorie <martin@mydomain.invalid> wrote:
On Mon, 25 Sep 2023 14:56:32 +0100, Andy Burns wrote:
Martin Gregorie wrote:Agreed, though the earlier parts of the login dialogue, which seem to
Have you got Wireshark installed? Using it to look at the traffic
between Chrome and your bank might suggest fixes.
You would hope communication to the bank would encrypted, which
somewhat complicates the process of deciphering https sessions with
wireshark
be where the OP's problems lie, may be plaintext: after you need to
have some sort of link up and running before you can turn encryption
on. If this initial part of starting an encrypted link is where the
OP's problem lies then I'd expect Wireshark could be quite useful.
There's no plaintext, it's all encrypted. All you can see there are the connections to various servers (and maybe their DNS) - everything inside those connections is encrypted.
Theo
On Mon, 25 Sep 2023 16:55:55 +0100, Davey wrote:
On 25 Sep 2023 16:28:01 +0100 (BST)
Theo <theom+news@chiark.greenend.org.uk> wrote:
Andy Burns <usenet@andyburns.uk> wrote:
Martin Gregorie wrote:
Have you got Wireshark installed? Using it to look at the
traffic between Chrome and your bank might suggest fixes.
You would hope communication to the bank would encrypted, which
somewhat complicates the process of deciphering https sessions
with wireshark
You can use your browser's Developer Tools to see the communication
between the browser and the site inside the HTTPS. But good luck
hunting for fixes: 'stuff talks to stuff' is as good as you'll get
really - there is too many layers of Javascript in there to easily
determine the problem, unless it's something very obvious like a
webserver taking forever to reply. It's a bit like trying to debug
Microsoft Office using a disassembler.
Theo
And all that the three of you have suggested sounds to be beyond my abilities.
But thank you for the ideas!.
Wireshark is a standard package for most Linux distros, and is pretty
simple to install and use, since all it does is to show the content
of incoming and outgoing messages and label each message to show
which stream it belongs to and whether its incoming or outgoing. It
also lets you capture the message flow as well as watching it stream
past on screen.
On 25 Sep 2023 18:34:13 +0100 (BST), Theo wrote:
There's no plaintext, it's all encrypted. All you can see there are
the connections to various servers (and maybe their DNS) - everything
inside those connections is encrypted.
I would expect the content of the session start/stop messages and
(probably) encryption start/stop messages to be plaintext, not least
because this stuff is public information: it has to be because its the routing and content type details (msg encrypted or plaintext) needed
to establish the mail transport sessions and would seem to what the
OP's system is complaining about.
Using Wireshark is about the simplest way I can think of to display this information: if its the same regardless connection success or failure then the problem is internal to the OP's system.
Similarly, if responses to these messages are error responses, munged or
not being returned, then the problem is internal to the OP's system.
If the problem is with the session establishment then I'd expect
Wireshark to confirm or deny this explanation and nothing more. If the session start request/response pairs are OK when displayed by
Wireshark, that the problem ir internam the the OP's system and its
time to look at his mail processes's debugging and diagnostic
capabilities.
Martin Gregorie <martin@mydomain.invalid> writes:with
On 25 Sep 2023 18:34:13 +0100 (BST), Theo wrote: =20
There's no plaintext, it's all encrypted. All you can see there
are the connections to various servers (and maybe their DNS) -
everything inside those connections is encrypted. =20
I would expect the content of the session start/stop messages and (probably) encryption start/stop messages to be plaintext, not least because this stuff is public information: it has to be because its=20
the routing and content type details (msg encrypted or plaintext)
needed to establish the mail transport sessions and would seem to
what the OP's system is complaining about. =20
The only things that are not encrypted are:
* DNS packets (maybe)
* TCP/IP headers
* The initial TLS key exchange messages (i.e. almost certainly just
the first two packets).
=20
The OP=E2=80=99s report is an HTTP status message, so an https session has been successfully established and something within that isn=E2=80=99t working. The handful of unencrypted parts are irrelevant. It also
references a well-known CDN and AWS Lambda: the immediate source of
the errors is inside HSBC and/or their suppliers, though presumably it=E2=80=99s triggered by some detail of the OP=E2=80=99s configuration.
=20
Using Wireshark is about the simplest way I can think of to display
this information: if its the same regardless connection success or
failure then the problem is internal to the OP's system.=20
Similarly, if responses to these messages are error responses,
munged or not being returned, then the problem is internal to the
OP's system.
If the problem is with the session establishment then I'd expect=20
Wireshark to confirm or deny this explanation and nothing more. If
the session start request/response pairs are OK when displayed by Wireshark, that the problem ir internam the the OP's system and its
time to look at his mail processes's debugging and diagnostic
capabilities. =20
Please read the OP=E2=80=99s original report, it is simply not consistent=
these possibilities.
=20
On Tue, 26 Sep 2023 08:17:42 +0100has
Richard Kettlewell <invalid@invalid.invalid> wrote:
=20
Martin Gregorie <martin@mydomain.invalid> writes: =20
On 25 Sep 2023 18:34:13 +0100 (BST), Theo wrote: =20
There's no plaintext, it's all encrypted. All you can see there
are the connections to various servers (and maybe their DNS) -
everything inside those connections is encrypted. =20
I would expect the content of the session start/stop messages and (probably) encryption start/stop messages to be plaintext, not=20
least because this stuff is public information: it has to be
because its the routing and content type details (msg encrypted
or plaintext) needed to establish the mail transport sessions and
would seem to what the OP's system is complaining about. =20
The only things that are not encrypted are:
* DNS packets (maybe)
* TCP/IP headers
* The initial TLS key exchange messages (i.e. almost certainly just
the first two packets).
=20
The OP=E2=80=99s report is an HTTP status message, so an https session =
ntbeen successfully established and something within that isn=E2=80=99t working. The handful of unencrypted parts are irrelevant. It also references a well-known CDN and AWS Lambda: the immediate source of
the errors is inside HSBC and/or their suppliers, though presumably it=E2=80=99s triggered by some detail of the OP=E2=80=99s configuration.
=20
Using Wireshark is about the simplest way I can think of to
display this information: if its the same regardless connection
success or failure then the problem is internal to the OP's
system.=20
Similarly, if responses to these messages are error responses,
munged or not being returned, then the problem is internal to the
OP's system.
If the problem is with the session establishment then I'd expect Wireshark to confirm or deny this explanation and nothing more. If=20
the session start request/response pairs are OK when displayed by Wireshark, that the problem ir internam the the OP's system and
its time to look at his mail processes's debugging and diagnostic capabilities. =20
Please read the OP=E2=80=99s original report, it is simply not consiste=
with these possibilities.=20
=20
Thank you for that clarification. It makes sense to me.
=20
Some more information:
=20
I tried:
a. Pausing Ghostery. No improvement.
b. AdBlock was not blocking anything, so nothing to do there.
c. Checked cookies, none listed for: HSBC, Lambda, or Cloudfront.
d. Luckily, the Test profile still works (fingers crossed).
e. I installed Wireshark, and again was confused by it. I do not know
it, and I cannot get beyond the Welcome screen with anything
useful. I need "Wireshark for Dummies". But hopefully, I don't need it
anyway.
f. Confirmed that Chrome still fails in the same way.
=20
Hmm.
=20
I have gone back to my Chrome browser and cleared everything that IKilled-off service workers?
can think of in there, but it still fails, with the same Error
message
Davey wrote:
I have gone back to my Chrome browser and cleared everything that IKilled-off service workers?
can think of in there, but it still fails, with the same Error
message
<chrome://serviceworker-internals>
I use Online Banking with HSBC on an almost daily basis, using Mozilla Firebird on Ubuntu.
Since Saturday, I only get an error message when I try to go to the
Sign-up page:
503 ERROR
The request could not be satisfied.
The Lambda function associated with the CloudFront distribution is
invalid or doesn't have the required permissions. We can't connect to
the server for this app or website at this time. There might be too
much traffic or a configuration error. Try again later, or contact the
app or website owner. If you provide content to customers through
CloudFront, you can find steps to troubleshoot and help prevent this
error by reviewing the CloudFront documentation.
I have researched this, and I have no idea what is usually discussed,
it is in a language level above my pay grade, but seems to say that it
is probably a problem with CloudFront, whoever they are.
If I use Chrome, still on Ubuntu, it works fine. That is always
updating whenever I do an update/upgrade.
What, if anything, can I do about this, apart from trying to contact
HSBC's annoying chatbot and explaining it to them? There have been no
recent updates to Mozilla, and there are none ready to download.
Any help gratefully received.
Davey <davey@example.invalid> wrote:
I use Online Banking with HSBC on an almost daily basis, using=20
Mozilla Firebird on Ubuntu.
Since Saturday, I only get an error message when I try to go to the
Sign-up page:
=20
503 ERROR
The request could not be satisfied.
The Lambda function associated with the CloudFront distribution is
invalid or doesn't have the required permissions. We can't connect
to the server for this app or website at this time. There might be
too much traffic or a configuration error. Try again later, or
contact the app or website owner. If you provide content to
customers through CloudFront, you can find steps to troubleshoot
and help prevent this error by reviewing the CloudFront
documentation.=20
=20
I have researched this, and I have no idea what is usually
discussed, it is in a language level above my pay grade, but seems
to say that it is probably a problem with CloudFront, whoever they
are. If I use Chrome, still on Ubuntu, it works fine. That is always updating whenever I do an update/upgrade.
=20
What, if anything, can I do about this, apart from trying to contact
HSBC's annoying chatbot and explaining it to them? There have been
no recent updates to Mozilla, and there are none ready to download.
=20
Any help gratefully received. =20
I wonder if your IP has become blacklisted in some way? If a server
has blocked it, that would explain the strange behaviour. It is
possible only one server of many is blocking, which would explain why
it sometimes works and sometimes doesn't. It's deep in the guts of
HSBC's infrastructure so there's not much hope of identifying which
server.
=20
Can you try from a different IP? For example if you have access to a
VPN try using that. Or use the portable hotspot feature on your
phone to tether to it and use mobile data.
=20
I had a quick look at 'www.hsbc.co.uk -> Login' in Firefox developer
tools - as expected there's a huge amount of Javascript stuff going
back and forth. It also pings a tracking/logging server about once a
second - uBlock Origin blocks that, but it still seems to work ok (I
didn't try logging in).
=20
Theo
Briefly, as I'm on my way out to a hospital appointment:
No other IP available.
Never tried tethering to my dumb 'phone, so no idea about that.
Although it might be worth learning!
Davey <davey@example.invalid> wrote:
Briefly, as I'm on my way out to a hospital appointment:
No other IP available.
Is it a laptop? You could take it somewhere with free wifi and try
there.
Never tried tethering to my dumb 'phone, so no idea about that.
Although it might be worth learning!
Not sure if your dumbphone can tether, some don't have wifi.
Theo
Davey wrote:
I have gone back to my Chrome browser and cleared everything that IKilled-off service workers?
can think of in there, but it still fails, with the same Error
message
<chrome://serviceworker-internals>
Returning to my current situation, what can I do with what I have, and
am capable of doing, as a way of eliminating various items to try to determine what is causing the problem? I have tried, repeatedly,
clearing the cache; Firefox's Troubleshooting procedure disables all
Add-ons, but that makes no difference. Can I temporarily disable some
cookies to try to home in on which one(s), if any, might be causing the
bad log-in? What else can I try?
The answer must be somewhere in the Profile configuration, it is a
question of digging out where it is.
Andy Burns wrote:
<chrome://serviceworker-internals>
Returning to my current situation, what can I do with what I have
You don't need to know *too* much about service workers, except they
can be quite powerful, acting as a stand-in for your bank's
webserver, complete with SQL data and their own process
On 27/09/2023 12:51, Davey wrote:
Returning to my current situation, what can I do with what I have,
and am capable of doing, as a way of eliminating various items to
try to determine what is causing the problem? I have tried,
repeatedly, clearing the cache; Firefox's Troubleshooting procedure disables all Add-ons, but that makes no difference. Can I
temporarily disable some cookies to try to home in on which one(s),
if any, might be causing the bad log-in? What else can I try?
The answer must be somewhere in the Profile configuration, it is a
question of digging out where it is.
It's been a long thread, and I'm not sure that I can remember all of
it, so apologies if this has been suggested before, but have you
tried:
Edit
Settings
Privacy & Security
Cookies & Site Data
Manage Data
Search for and delete the cookies and data for your bank.
On Wed, 27 Sep 2023 13:32:11 +0100
Java Jive <java@evij.com.invalid> wrote:
On 27/09/2023 12:51, Davey wrote:
Returning to my current situation, what can I do with what I have,
and am capable of doing, as a way of eliminating various items to
try to determine what is causing the problem? I have tried,
repeatedly, clearing the cache; Firefox's Troubleshooting
procedure disables all Add-ons, but that makes no difference. Can
I temporarily disable some cookies to try to home in on which
one(s), if any, might be causing the bad log-in? What else can I
try?
The answer must be somewhere in the Profile configuration, it is a question of digging out where it is.
It's been a long thread, and I'm not sure that I can remember all of
it, so apologies if this has been suggested before, but have you
tried:
Edit
Settings
Privacy & Security
Cookies & Site Data
Manage Data
Search for and delete the cookies and data for your bank.
I searched through my cookies for anything related to: HSBC, Lambda, CloudFront, but with no joy with any of them.
If I could make head or tail of the service-workers thing, that might
help.
Am 24.09.2023 um 11:10:23 Uhr schrieb Davey:
I managed to talk to a human (!), but she could find no reference to
anybody else with similar problems reported. She suggested I do a
Browser Reset.
Did you try it in a fresh firefox profile?
Go to about:profiles to create it.
| Sysop: | Luis Silva |
|---|---|
| Location: | Lisbon |
| Users: | 763 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 179:33:02 |
| Calls: | 111 |
| Files: | 46,971 |
| Messages: | 11,214 |