@ jacadcaps - I was going to mention yesterday, but I managed to get logged in, though it may have been with v4.3, though it was v4.4 that I was having issues with accessing ebay UK site - Signing In with, that I hadn't been having with v4.3, usually related to the HTTP/2 framing layer, the actual message:

Error loading www.ebay.co.uk
92: Stream error in the HTTP/2 framing layer

. . . that was the message that I got more often than others with v4.4, but often the login process was taking too long and it sometimes just gave a timing out error message, because it had taken too long to process the request.

It still seems to be the case with v4.5! . . . at least for me, sadly.

I have deleted all my cookies, which I also did with v4.4, so that is not one of the factors as far as I can tell.

I enter my password and wait, and wait, and then I get either the time out message or the HTTP/2 message, but if I click the bookmark link again I can then usually, find that the login process has completed, but the page errored before completing the entire process.

After I have used v4.4 or v4.5 I seem to have issues using v4.3, prior to any reboot, so I don't know if it is affecting the network in some way, leaving some error in the network itself that then affects using the system, which seems weird I know but I cannot explain it any other way . . . well not at the moment!

I even got . . .

Error loading morph.zone
52: Server returned nothing (no headers, no data)

and . . .

SSL Error loading www.amazon.co.uk
35: SSL connect error

However, even transferring from one page to another often causes one of the two message to occur, and I have to try again, and it is getting quite frustrating using Wayfarer v4.5, or v4.4 on many websites as I get such messages. I am wondering if it would be better for me to swap back to v4.3 for the time being, until whatever these issues are get isolated and addressed so I can have confidence that Wayfarer is back to normal!

pffft! Updates come quicker then I can test.....

\0/

4.5 is now out to address an issue with libcURL and HTTP/2.

Thanks much for the awesome support!

Quote:

@matt

Sent you a PM with a link to a test version. Let me know if that one works.

Yes sir. I enter the entire https://192.168.0.1:321

For the fun of it I booted up my Powerbook and guess what, it worked just fine. I'm not sure I get it at this point... :).

To recap. I just got a 2.7 Powermac into production with a fresh install of 3.17. Installed SSL and the security update. This system as far as I know never connected to the Nas via the web interface. This system is pretty much identical to the 2.3 that I retired because of ram issues that impacted my accounting software (funny as it did run the web interface).

I tried to look at the network settings (using the onboard gigabit nic just like I did on the 2.3), Wayfarer, and reinstalled SSL.

Strange. Again, not the most critical thing to worry about...

Thanks guys,

M


Quote:

Quote:
Just to make sure you enter https://192.168.0.1:321 and not just the address without the scheme?

The NAS has a firewall update the other week, not sure if that could have caused it. But my windows pc doesn't have any issues.

4.3 still has the same issue. The last time I logged into the nas was on my other box. I installed SSL and the security update for 3.17.

I tried the refresh and it didn't work.

I know the NAS requires HTTPS to connect and I'm using a different port so I have to put it in the url. (192.168.0.1:321).

This isn't critical since smbfs still works fine (although with multiple shares it loses itself, but perfectly stable with 1 share.) and that is what truly important to me.

Just strange that it used to work on the other box and not this one. May I have a setting I have overlooked...

And how about if you try again (reload)?

Does it happen with 4.3 as well? Sure it wasn’t some update to your NAS that broke things?

Can't connect to my NAS any longer.

Getting an error:
With HTTPS:
92: Stream error in the HTTP/2 framing layer

With HTTP:
Bad Request

Your browser sent a request that this server could not understand.
Reason: You're speaking plain HTTP to an SSL-enabled server port.
Instead use the HTTPS scheme to access this URL, please.

Hi jacadcaps,

thanks a lot for this new update!

Good version reuploaded on MorphOS-Storage

[EDIT] no readme file in the archive ?

[ Edité par Papiosaur 28.11.2022 - 09:57 ]

A small bug crept in and the archive was just updated. The correct Wayfarer binary has an md5 of 0bf585270f7f2246a47ab47f88279a8e.

Please re-download if you've already installed 4.4.

Quote:

I've spent a considerable amount of time trying to debug this and it appears to be a bug in ffmpeg itself (happens with versions 3, 4 and 5 at least). I'll see if I can find the time to report a bug to ffmpeg, but unless they decide to fix it, I'm afraid it's not going to be improved in Wayfarer.

Wayfarer 4.4 is now out!

- Massive performance gains in decoding of large file images
- Loading progress bar colour can now be configured in Interface settings
- Cherrypicked OffscreenCanvas fixes from latest WebKit sources
- Added handling of very long filenames when finalizing a download
- Fixed a bad free call in the media decoder
- Disabled some stray debug

@Cool_amigaN

Fixed in the upcoming update.

Well, I found a little problem with mail boxes open with Wayfarer, when you write your e-mail and you use accents in spanish language, like this á-í-ó, Wayfarer shows thats 'a-'o

I 've tried downloading a torrent file which had a file name length of 109 chars (including the .torrent extension). In retrospect and upon some testing, it exceeds the max file name length of Ambient by 2 chars, right?

Anyway, though Wayfarer displays the full name on the downloading requester correctly, it failed with a message "i/o error rename".

I then tried with OWB and it failed too. But the error message on Wayfarer gave me a hint and since OWB allows you to type a new name upon clicking downloading, I was able to shorten the file name, download it and then add it to dizzytorrent.

So, my question is, in order to avoid a similar confusion, why not add a similar rename requester to Wayfarer too? Perhaps the requester could be optionally enabled on its settings for suspicious users :P

[ Edited by Cool_amigaN 21.11.2022 - 23:54 ]

@Templario : did you try to open Wayfarer is in own screen and disabled enhanced display for this screen ? Maybe best speed for the show.

Quote:

Thnak you for your suggestion.

> With Facebook web, wayfarer goes slow, any trick to show the page more fast?

Try m.facebook.com, which is more lightweight.

AmigaHarry2: i have tried Aldo with ethernet cable directly on the netbox 1gb Switch ...and same result 500kb/s max ...and Owb 1.5mb/s , ftp rules great btw my pc and my powerbook. I have tried with other dns same result..the only gain ils that cable is better because of the faster ping.
So reactivness is better but for site like official morphos with a Big background it's slow.

@Templario

Keep in mind that the JavaScript support in Wayfarer is only interpreted. On x86 WebKit there is an elaborate 4-stage JIT.

With Facebook web, wayfarer goes slow, any trick to show the page more fast?