Does anything happen if you wait 3-4 mins more?
I have seen this being very slow to load first time through.
3 Likes
So, after a long wait, I got a little more logs in dweb.
DEBUG www_handler(/)...
DEBUG our_directory_version:
port: 44096
history_address: Some(HistoryAddress { owner: PublicKey(19e3..b297) })
version: None
archive_address: 97380ec06a76d202c728d49d43a22fe40db96de1f130ab11d5b1fac3d46778b0
Splitting path '/'
...into '/' and ''
Looking for resource at '/'
Retrying for index file in new_resource_path '/'
DEBUG looking for a default INDEX file, one of ["index.html", "index.htm"]
DEBUG lookup_name_in_vec(index.html)
DEBUG lookup_name_in_vec(index.htm)
DEBUG: immutable data with eTag: "immutable-11254693861628017524-text/html"
DEBUG ETAG COMPARING: "immutable-11254693861628017524-text/html" and "immutable-11254693861628017524-text/html"
DEBUG serve with ports HttpResponse: 304 Not Modified (Not Modified)
Here is the console from Brave
1 Like
Unfortunately, I’ve waited over 30 minutes.
3 Likes
I have no idea if that is useful for you @happybeing, I am a complete noob in all of these things, with basic knowledge… but I am curious person and I wanted to try dweb and Atlas, so… I started with a fresh install of Ubuntu.
Then I tried to install Rust with the command curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh, didn’t work, I had to install curl first but that was easy with sudo apt-get install curl 
So, with Rust installed, I then used your dweb install command cargo install --locked dweb-cli however I ran into issues that were fixed with sudo apt install build-essential and sudo apt install libssl-dev. Only after that I was able to actually run dweb serve and see the Swagger UI or Atlas.
I know it may be funny for most of you, but this took me several hours and even after all of these hurdles, Atlas is loading and loading and I have no idea of how to import my wallet there or to actually post something.
You guys are great and now I can really see ‘something’ but still - this is too complicated for 99% of people I guess. But at least, I can see the light at the end of the tunnel and thank you for that 
9 Likes
if you already have the private key for your wallet and some ant and eth in it.
edit your bashrc file to pre set wallet and some options
nano ~/.bashrc
paste this at the end of the file with your private key
export EVM_NETWORK=arbitrum-one
export SECRET_KEY=<YOUR WALLET PRIVATE KEY>
export CHUNK_UPLOAD_BATCH_SIZE=4
export CHUNK_DOWNLOAD_BATCH_SIZE=16
export FILE_UPLOAD_BATCH_SIZE=4
export UPLOAD_FLOW_BATCH_SIZE=100
close the terminal window and reopen for changes to take affect the restart dweb
you can play around with those values to fine tune the client those are the values I am using at the moment.
2 Likes
Oh God, that is another day for me to understand what you have just said These CLI and terminals are very painful for me. I will try, thank you.
6 Likes
hopefully it will be gui’s in the near future and will not need to be looking at terminal.
but you can always say you were there in the trenches doing it on the command line when it all began.
if you need more help dont be scared to ask
3 Likes
I’d like to run dweb on my Pi and access the dweb server from my laptop. It only listens for connections on 127.0.0.1:8080 though. The Pi doesn’t have a GUI. I could put one on but that would tie me to sitting at it. Then I’d also be able to use it by VPNing to my home when I’m away.
I can’t see any options for changing what it listens on.
If it’s not possible at the moment can this be a feature request?
I love it by the way! And the best thing about it is it’s opening up possibilities for other apps.
v0.91 now listens on 5537.
Your can change port and host with --port PORT and --host HOST
I target the help at ordinary folk so those and other advanced options are hidden, sorry!
Let us know how you get on, this will be handy to document if you get it working. I think @ambled has had success with these options.
1 Like
Ah! Amazing! I’ll give it a go. After posting I realised this machine was on 0.7.1 so I’m updating just now.
1 Like
I got a big load of errors at the end of the cargo install of dweb:-
Some errors have detailed explanations: E0432, E0599.
For more information about an error, try `rustc --explain E0432`.
error: could not compile `autonomi` (lib) due to 40 previous errors
warning: build failed, waiting for other jobs to finish...
error: failed to compile `dweb-cli v0.9.1`, intermediate artifacts can be found at `/tmp/cargo-installNNNjdM`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.
Full text of errors:-
dweb_compile_error.txt.zip (2.9 KB)
I’ve done a ‘rustup update’ which updated rustc from 1.87.0 to 1.88.0 but got the same errors again.
1 Like
Can you go through the instructions in the readme, and after that doesn’t work try cargo install --locked dweb-cli.
I don’t have time to dig through errors at the moment but if you still have problems someone else might be able to help.
I’ll also look into an arm build when I can.
Thanks for blazing this trail - please report back if you can. 
2 Likes
I had some errors and dropping the locked sorted the problem cargo install dweb-cli
Well that’s a new one! Good to know 
1 Like
With locked failed with some warnings so tried that as first idea before bothering you and it worked so I didn’t ask any questions 
1 Like
Very wise, because I don’t have any answers.
2 Likes
I suspect you have lots of Pimms though
2 Likes
I think running dweb on one computer and connecting to it from another can’t be done at this time. Below is what I got in the console from dweb after starting it with:-
dweb serve --port 5537 --host 10.0.0.21
then starting Atlas with:-
dweb open --port 5537 --host 10.0.0.21 99e3b8df52814b379e216caf797426071000905a2cd93a9f5e90eef2b32517a9ec1ef0bfe27d79360014fd97639ac612
which produced this on the console:-
DEBUG url: http://10.0.0.21:5537/dweb-open/v/99e3b8df52814b379e216caf797426071000905a2cd93a9f5e90eef2b32517a9ec1ef0bfe27d79360014fd97639ac612/
On the console from dweb:-
DEBUG serve with ports HttpRequest : GET /dweb-open/v/99e3b8df52814b379e216caf797426071000905a2cd93a9f5e90eef2b32517a9ec1ef0bfe27d79360014fd97639ac612/
DEBUG /dweb-open/v/99e3b8df52814b379e216caf797426071000905a2cd93a9f5e90eef2b32517a9ec1ef0bfe27d79360014fd97639ac612/
DEBUG parse_versioned_path_params_with_as_name() v/99e3b8df52814b379e216caf797426071000905a2cd93a9f5e90eef2b32517a9ec1ef0bfe27d79360014fd97639ac612/
1:v 2: 99e3b8df52814b379e216caf797426071000905a2cd93a9f5e90eef2b32517a9ec1ef0bfe27d79360014fd97639ac612 r:
version:None as_name: anonymous, address_or_name: 99e3b8df52814b379e216caf797426071000905a2cd93a9f5e90eef2b32517a9ec1ef0bfe27d79360014fd97639ac612 remote_path:
DEBUG History::from_history_address(99e3b8df52814b379e216caf797426071000905a2cd93a9f5e90eef2b32517a9ec1ef0bfe27d79360014fd97639ac612)
>>TRYING pointer_get() unlimited times...
>>TRY 1 of unlimited
DEBUG pointer counter: 62, head address: 8bb5db75476cfc81c9e9a42bfeb03c6f90aed1196a086af8c24d60891c54df4b5f9a10d41802f8f3662851f4471696d5
>>OK
DEBUG INSPECT pointer_counter: 62
DEBUG INSPECT pointer_target : 8bb5db75476cfc81c9e9a42bfeb03c6f90aed1196a086af8c24d60891c54df4b5f9a10d41802f8f3662851f4471696d5
DEBUG from_history_address() returning History with num_entries: 63
DEBUG History::get_version_entry_value(version: 62)
DEBUG History::get_entry_value(index: 62)
DEBUG from_archive_address() at 26892745c4697675c923ef74967b77e1256493fe70a5a8982eaba5f0485ad6e7
DEBUG DualArchive attempting to deserialise as PrivateArchive...
DEBUG Retrieved PrivateArchive of 5 files
DEBUG Tree initialised using PrivateArchive
Started a dweb server listening on 127.0.0.1:44119 for version None at Some(HistoryAddress { owner: PublicKey(19e3..b297) }) -> 26892745c4697675c923ef74967b77e1256493fe70a5a8982eaba5f0485ad6e7
DEBUG req.full_url(): http://10.0.0.21:5537/dweb-open/v/99e3b8df52814b379e216caf797426071000905a2cd93a9f5e90eef2b32517a9ec1ef0bfe27d79360014fd97639ac612/
DEBUG scheme : http
DEBUG port : :44119
DEBUG response_redirect() redirecting to http://127.0.0.1:44119
DEBUG serve with ports HttpResponse: 303 See Other (See Other)
after I’d tried to access http://10.0.0.21:5537/dweb-open/v/99e3b8df52814b379e216caf797426071000905a2cd93a9f5e90eef2b32517a9ec1ef0bfe27d79360014fd97639ac612/
from my laptop.
Which suggests there is something making a redirect to 127.0.0.1.
So I think that’s as far as I can get at the moment.
Yeh, I’ve not tested this or worried about it so think this is a bug. I’m busy but this might be easy to fix so will let you know when I have something. I created an issue for it here:
Thanks for having a go at this and giving such helpful details about the issue.
5 Likes
dweb v0.10.0
I’ve published a version which updates to autonomi v0.5.0 which includes the Client Light Networking changes.
Changes
I don’t know if or how this will affect dweb publishing but let’s hope all clients get the benefits!
Note to devs
The Autonomi update has some breaking changes which may affect dweb apps using the REST API, but hopefully not. The main one is the Pointer counter and History version is now u64, so look out for that dweb devs! See releases for more.
Updating
Update either with:
cargo install dweb-cli
Or download the v0.10.0 build for Windows, Mac or Linux here:
8 Likes