mirror of
https://github.com/YunoHost/doc.git
synced 2024-09-03 20:06:26 +02:00
[fix] AngryIP screenshot
This commit is contained in:
parent
dd8002493b
commit
7fc69341c7
2 changed files with 41 additions and 6 deletions
BIN
images/angryip.png
Normal file
BIN
images/angryip.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 74 KiB |
|
@ -9,15 +9,50 @@ routes:
|
||||||
|
|
||||||
On an installation at home, your server should typically be accessible using the `yunohost.local` domain. If for any reason this does not work, you may need to find the *local* IP of your server.
|
On an installation at home, your server should typically be accessible using the `yunohost.local` domain. If for any reason this does not work, you may need to find the *local* IP of your server.
|
||||||
|
|
||||||
The local IP is the address used to refer to your server inside the local network (typically your home) where multiple devices are connected to a router (your internet box). The local IP typically looks like `192.168.x.y` (or sometimes `10.0.x.y`)
|
## What is a local IP ?
|
||||||
|
The local IP is the address used to refer to your server inside the local network (typically your home) where multiple devices are connected to a router (your internet box). The local IP typically looks like `192.168.x.y` (or sometimes `10.0.x.y` or `172.16.x.y`)
|
||||||
|
|
||||||
|
## How to find it ?
|
||||||
Any of these tricks should allow you to find the local IP of your server:
|
Any of these tricks should allow you to find the local IP of your server:
|
||||||
|
[ui-tabs position="top-left" active="0" theme="lite"]
|
||||||
|
[ui-tab title="(Recommended) With AngryIP"]
|
||||||
|
|
||||||
- Use the [AngryIP](https://angryip.org/download/) software
|
You can use the [AngryIP](https://angryip.org/download/) software to achieve that. You just need to scan these local ip ranges in this order until you find some active IP:
|
||||||
- Connect to your internet box / router interface to list the machines connected, or check the logs;
|
- 192.168.0.0 -> 192.168.0.255
|
||||||
- If you're using Linux, you can open a terminal and use `sudo arp-scan --local` to list the IP on your local network (this may also work in Windows);
|
- 192.168.1.0 -> 192.168.1.255
|
||||||
- If the `arp-scan` command displays a confusing number of devices, you can check which ones are open to SSH with `nmap -p 22 192.168.1.0/24` to sort them out (adapt the IP range to your local network)
|
- 192.168.2.0 -> 192.168.255.255
|
||||||
- Plug a screen on your server, log in and type `hostname --all-ip-address`.
|
- 10.0.0.0 -> 10.0.255.255
|
||||||
|
- 172.16.0.0 -> 172.31.255.255
|
||||||
|
|
||||||
|
!!! Tips: you can order by ping like on this image.
|
||||||
|
|
||||||
|
![](image://angryip.png?class=inline)
|
||||||
|
|
||||||
|
If you find some IPs with a ping, you can try to type it directly in a browser and see if it's a yunohost or not.
|
||||||
|
|
||||||
|
[/ui-tab]
|
||||||
|
[ui-tab title="With your internet router / box"]
|
||||||
|
Connect to your internet box / router interface to list the machines connected.
|
||||||
|
[/ui-tab]
|
||||||
|
[ui-tab title="With arp-scan"]
|
||||||
|
If you're using Linux, you can open a terminal and use `sudo arp-scan --local` to list the IP on your local network (this may also work in Windows);
|
||||||
|
|
||||||
|
If the `arp-scan` command displays a confusing number of devices, you can check which ones are open to SSH with `nmap -p 22 192.168.1.0/24` to sort them out (adapt the IP range to your local network)
|
||||||
|
[/ui-tab]
|
||||||
|
[ui-tab title="With a screen"]
|
||||||
|
Plug a screen on your server, log in and type `hostname --all-ip-address`.
|
||||||
|
|
||||||
|
If you don't know credentials to login, try the following default credentials:
|
||||||
|
|
||||||
|
| login | password |
|
||||||
|
|---|---|
|
||||||
|
| root | yunohost |
|
||||||
|
| root | 1234 |
|
||||||
|
|
||||||
|
[/ui-tab]
|
||||||
|
[/ui-tabs]
|
||||||
|
|
||||||
|
## I still can't find my local IP
|
||||||
|
|
||||||
If you are unable to find your server using any of the previous tricks, maybe your server did not boot correctly:
|
If you are unable to find your server using any of the previous tricks, maybe your server did not boot correctly:
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue