Something wrong? Or only Gateway issue?

Irgendetwas falsch? Oder nur Gateway zurzeit überlastet?

Something wrong? Or only Gateway issue?

See also: New project: a new blog on the IPFS

[code]$ ipfs files ls -l
ipfs-blog/ QmexQwE1qzacU2JEs7nc3LB1t9AQpbqwhgSZks2VwLtwJG 0

$ ipfs files ls -l /ipfs-blog
index.html QmabprM1WeCYZxUjHQK2hjxK49zciMAponHRDoPVgHXiGG 1736
media/ QmapTUbSkJHndQDSxA7ArMmN3ZJrF5ZKebpkFXMDLCxfiM 0
pages/ QmUb4sCEtdNjYws5mrfYkMTLXwr3GFKpAGhY1mbqKnUSZ1 0
template.html QmY3G7ztuVZQaxLfw9A54Md3B83TWiyq8aRcDaHvS5vJTE 309[/code]


$ wget URL transformed to HTTPS due to an HSTS policy --2019-12-21 11:54:55-- Auflösen des Hostnamens (…, 2602:fea2:2::1 Verbindungsaufbau zu (||:443 … verbunden. HTTP-Anforderung gesendet, auf Antwort wird gewartet … 504 Gateway Time-out Erneuter Versuch.

and approx. 10 minutes later …

--2019-12-21 12:05:04-- (Versuch: 2) Wiederverwendung der bestehenden Verbindung zu HTTP-Anforderung gesendet, auf Antwort wird gewartet …

but this works!

$ ipfs get /ipfs/QmexQwE1qzacU2JEs7nc3LB1t9AQpbqwhgSZks2VwLtwJG/index.html Saving file(s) to index.html 1.70 KiB / 1.70 KiB [============================================================================================================================] 100.00% 0s

Is your IPFS daemon reachable from the gateways?

ipfs id should show addresses that your daemon is announcing.

At least one of those addresses should be a public IP that can be contacted from the outside.

If not, gateways will mostly not be able to retrieve that content. Usually some magic port-opening happens using uPnP but some routers/networks ignore this. As a workaround, Announce-Addresses can be configured manually in the .ipfs/config, and you can stick a public address you want to advertise and open the chosen port manually in the router (should link to :4001, the ipfs-swarm port).