Hi,

I did change my network and fixed some things and I am now able to reach 
the topology container via nginx an the internal url.
I also get the mentioned message response back with the curl command, but 
when I try to access the url via Chrome, it says the endpoint does not 
exist.
The only output produced in the topology logs are that the endpoints are 
not found.
Maybe my traefik specific configuration is making some problems here?

Best regards,
Mirza

On Tuesday, August 11, 2020 at 11:50:24 AM UTC+2, Ajay Tripathi wrote:
>
> Hi,
>  
>
>> Is there a tutorial on how to setup it up and debug stuff (endpoints for 
>> testing maybe?) so I can debug it myself.
>>
>
> You can set the `DEBUG_MODE` variable in `.env` file to `True`, then go to 
> the `http://topology.wisp.example.org/api/v1/` 
> <http://topology.wisp.example.org/api/v1/> URL on your browser.
> That should help you debug if there is an error in the API.
>
> However, I think that you''ve made changes to the network, so it's 
> possible that controller is not able to access network-topology container.
>
> In that case, you'll have to:
>
> 1. docker exec -it docker-openwisp_controller_1 bash 
> 2. apt update & apt install curl
> 3. curl topology.internal/api/v1/ 
>
> You should see the django error page ending with "You're seeing this error 
> because you have <code>DEBUG = True</code>". Which means, the containers 
> are able to communicate.
>
> Lastly, docker-compose logs:
>
> 1. docker-compose logs topology
> 2. docker-compose logs controller should help to spot any errors once 
> `DEBUG_MODE=True` is enabled.
>
> This information should help you get started with debugging, let me know 
> if there anything else I should mention.
>
>
> Best,
> Ajay Tripathi
>


-- 
You received this message because you are subscribed to the Google Groups 
"OpenWISP" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/08bec5c1-4af7-4977-8b21-5592229011a1o%40googlegroups.com.

Reply via email to