Baby Fleming Public Shared Section

@StephenC @JPL from what i see in JPL’s screenshot CLI is not even trying to use authd at that point, CLI first creates the test-coins directly to the network, and that’s the step is failing there, once the test-coins are created CLI will send the request to authd to create the account using those test-coins. So it seems you are having issue to connect to the network, can you please try safe keys create --test-coins, that should fail if you still have issue to bootstrap.

Edit: a firewall issue perhaps? can you also see what kind of info you get doing RUST_LOG=debug safe keys create --test-coins ? that should help us probably understand why it cannot bootstrap

2 Likes

Awesome achievement with the publicly hosted section! Great job!

I ran the CLI commands and were able to connect and upload an image file. However since the current version of the SAFE Browser I can’t get it running. All previous versions worked without any problems. Here is what I did (Win10 64):

  1. Deinstalled the old browser version
  2. Installed the new version with administration rights
  3. Connected to the shared section network
  4. Ran the new version with administration rights
  5. The process (actually it displays 3 processes) seems to start, but no browser window opens

The same behavior happens when I try to start the browser without a running auth service. So the problem seems independent to the vault network connection. Does the browser create any log files? I couldn’t find any. Anyone else running in this issue?

@Mindphreaker I’m not fully sure, but running it as admin perhaps is causing issues to the browser not being able to connect to authd as it probably cannot find authd QUIC certificates. Is there any reason why you run it as admin? can you try running everything as a regular (and same) user?

Not sure whether this is causing @Mindphreaker’s problem but I’ve just noticed there’s an issue with the signature of the browser exe for Windows - investigating

1 Like

Because for the auth service to start the PowerShell needs to be run as admin, therefore I still had the same shell open and thought it might be a good idea to run the browser as well as admin.

I’m now running everything without admin rights and also re-installed the browser without admin rights but still the same behavior. Running processes but no window.

nothing shows! Waht am I wrong here ? :stuck_out_tongue:

I thought the same - took a good few seconds but it did eventually load for me :smiley:

1 Like

Right, to install and start authd you need admin, but it will set it up still so it works with the regular user. I started right now refactoring authd for Windows so we don’t need this admin perms anymore as they are clearly not ideal.

Once you have the authd running, you shouldn’t need admin perms for anything else, none of the apps we are developing and releasing.

1 Like

Is there an option to list FilesContainers?..
I have one which I uploaded to last night… would like to attribute nrs name to it but didn’t note the string that is that FilesContainer.

Unfortunately not at this point, this will be possible whenever we have the labeling for data implemented.

2 Likes

Got a safe:// URL for that yet? :slight_smile:

Just downloading the browser to look see if safe://hello now works.

Surprised that it is a matter of safe nrs to the index.html that works and not the FileContainer as a pointer, perhaps there is no standard to ensure the browser knows what files to look to… but then a cycle through the normal perhaps would work… index.html; index.htm; etc … that as a standard and/or something like .htaccess that is so well used.

safe://hello works as index.html but hasn’t picked up on the .css sat in the same container.

+  ./to-upload/hello/www/favicon.ico  safe://hbwybyddc49peadeqqbpfn75wmitabsoiwsdw7j9spcytb4k5crin6refu 
+  ./to-upload/hello/www/index.html   safe://hbhybyns97ejsb46bryguc345hokaugu9apnfzscakm4keh9kn6zuneby3 
+  ./to-upload/hello/www/style.css    safe://hbhyyyd446wnju9gouch43qfaj1b9eoss4wadnm8yffdnihwu3iuipsd7r 
1 Like

Your favourite PC is back to haunt you!

John@John-HP MINGW64 /c/users/John/Documents/SAFEnetwork/_safe-cli
$ RUST_LOG=debug ./safe keys create --test-coins
[2020-04-01T14:54:14Z DEBUG safe] Starting SAFE CLI...
[2020-04-01T14:54:14Z DEBUG safe::cli] Processing command: CmdArgs { cmd: Some(K                                            eys(Create { pay_with: None, test_coins: true, preload: None, pk: None })), outp                                            ut_fmt: None, output_json: false, dry: false, xorurl_base: None, endpoint: None                                             }
[2020-04-01T14:54:14Z WARN  safe::subcommands::keys] Note that the SafeKey to be                                             created will be preloaded with **test coins** rather than real coins
[2020-04-01T14:54:14Z WARN  safe::subcommands::keys] You can pass a preload amou                                            nt with test-coins, 1000.111 will be added by default.
[2020-04-01T14:54:14Z INFO  safe_api::api::app::safe_client_libs] Creating test                                             SafeKey with 1000.111000000 test coins
[2020-04-01T14:54:14Z DEBUG quic_p2p::connect] Connecting to 167.71.140.27:443
[2020-04-01T14:54:14Z DEBUG rustls::client::hs] No cached session for DNSNameRef                                            ("maidsafe.net")
[2020-04-01T14:54:14Z DEBUG rustls::client::hs] Not resuming any session
[2020-04-01T14:54:44Z DEBUG quic_p2p::connect] Error connecting to peer 167.71.140.27:443: Connection(TimedOut) - Details: Connection lost
[2020-04-01T14:54:44Z INFO  quic_p2p::connect] Peer 167.71.140.27:443 has a connection to us but we couldn't connect to it. All connections to this peer will now be severed.
[2020-04-01T14:54:44Z DEBUG quic_p2p::event_loop] Exiting QuicP2p Event Loop
[2020-04-01T14:54:44Z DEBUG quic_p2p::connect] Connecting to 167.71.140.27:443
[2020-04-01T14:54:44Z DEBUG rustls::client::hs] No cached session for DNSNameRef("maidsafe.net")
[2020-04-01T14:54:44Z DEBUG rustls::client::hs] Not resuming any session
[2020-04-01T14:55:14Z DEBUG quic_p2p::connect] Error connecting to peer 167.71.140.27:443: Connection(TimedOut) - Details: Connection lost
[2020-04-01T14:55:14Z INFO  quic_p2p::connect] Peer 167.71.140.27:443 has a connection to us but we couldn't connect to it. All connections to this peer will now be severed.
[2020-04-01T14:55:14Z DEBUG quic_p2p::event_loop] Exiting QuicP2p Event Loop
[2020-04-01T14:55:14Z DEBUG quic_p2p::connect] Connecting to 167.71.140.27:443
[2020-04-01T14:55:14Z DEBUG rustls::client::hs] No cached session for DNSNameRef("maidsafe.net")
[2020-04-01T14:55:14Z DEBUG rustls::client::hs] Not resuming any session
[2020-04-01T14:55:44Z DEBUG quic_p2p::connect] Error connecting to peer 167.71.140.27:443: Connection(TimedOut) - Details: Connection lost
[2020-04-01T14:55:44Z INFO  quic_p2p::connect] Peer 167.71.140.27:443 has a connection to us but we couldn't connect to it. All connections to this peer will now be severed.
[2020-04-01T14:55:44Z DEBUG quic_p2p::event_loop] Exiting QuicP2p Event Loop
[2020-04-01T14:55:44Z ERROR safe] safe-cli error: [Error] NetDataError - Failed to allocate test coins: Unexpected: Connection timed out when bootstrapping to the network - CoreError::Unexpected::{"Connection timed out when bootstrapping to the network"}
5 Likes

Good sleuthing devs. It’s all just working as expected here on Ubuntu 18.04.
I’ll see if I can recreate on son#2’s Win10 machine that is doing nothing meantime

1 Like

On Linux Mint had to make the file executable, which was a guess at a file extension I’d not seen before .AppImage

Browser works but
Terminal puts out this, in case useful:

$ ./safe-browser-v0.17.0-alpha.1-linux-x64.AppImage 
(node:9387) DeprecationWarning: file property is deprecated and will be removed in v5.
(node:9387) DeprecationWarning: file property is deprecated and will be removed in v5.
15:58:14.406 › error reading mySites data. {
  constructor: 'Error',
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/home/safe/.config/SAFE Browser/mySites.json',
  stack: "Error: ENOENT: no such file or directory, open '/home/safe/.config/SAFE Browser/mySites.json'"
}
(node:9387) ProtocolDeprecateCallback: The callback argument of protocol module APIs is no longer needed.
(node:9387) ProtocolDeprecateCallback: The callback argument of protocol module APIs is no longer needed.
15:58:33.299 › url must be a string
(electron) 'getUserAgent function' is deprecated and will be removed. Please use 'userAgent property' instead.
(electron) 'setUserAgent function' is deprecated and will be removed. Please use 'userAgent property' instead.
2 Likes

A couple of sites:

safe://wave1.digipl
safe://testaudio.digipl

But the first one has erratic behavior. Sometimes the image is right but sometimes it’s not.
There’s also some mess with the versions but that,maybe, has been my fault when playing with sub-names.

Image good:

Image with errors:

8 Likes

Cool, I’ll have a look. I’m seeing how many tabs I can get open on the browser before I break it :slight_smile:

Cos I’m not happy until I’ve broken something…

1 Like

now this IS good, well it could be good :slight_smile:
Excellent idea, I tried to report my results but on clicking report results I got a blank page.
Of course it is VERY early days yet but this is a wonderful initiative. Well done :clap: :clap: :clap:

Results were mostly “Partly” - if you din’t actually get the report.

When you get a chance to work on this some more, please consider a comments box next to each audio format. MP3 just works as expected. Opus has great quality but other formats mostly were truncated and finished early but with good quality.

1 Like

Important Note for any potential Windows users of the new desktop Browser Alpha version - there was an issue where CI did not sign the exe correctly so the auto upgrade through the browser is not working. I have signed manually & uploaded a working exe to the GitHub release page here, however it’s not quite as straight forward for the auto update through the browser itself so I’ll need to continue with the help of @joshuef tomorrow to resolve that and get auto-update working again (probably needs another CI run but we need to find out what went wrong with signing this time).

In the meantime, any Windows users wishing to update to the Browser version which works with the shared vault should manually uninstall the old browser version from their system, download the Windows exe from the GitHub release page and install it manually.

I’ll add a note to the OP.

2 Likes

Strange, I did exactly that but it doesn’t work. The previous version works without any problems, so something else might have changed.