PlumberDeploy says API is active on DO, but URL not accessible?

I have (I think) deployed a plumber API on a DigitalOcean droplet. The droplet has R & plumber installed (I verified by going into the console). When I used do_deploy_api, R uploaded my directory files and ended with this:

● plumber-geovalidate.service - Plumber API
     Loaded: loaded (/etc/systemd/system/plumber-geovalidate.service; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2022-10-13 03:04:45 UTC; 2s ago
   Main PID: 43431 (R)
      Tasks: 2 (limit: 1131)
     Memory: 252.4M
     CGroup: /system.slice/plumber-geovalidate.service
             └─43431 /usr/lib/R/bin/exec/R --no-echo --no-restore -e pr~+~<-~+~plumber::pr('/var/plumber/geovalidate/plumber.R');~+~pr$setDocs(FALSE);~+~~+~pr$run(port=8000)
[100%] C:\Users\W530\AppData\Local\Temp\Rtmpiw5SiD\file3dc0450b6c70
**Api root url is droplet likely not up yet/geovalidate. Any endpoints from api will be served relative to this root**.

The deployment completed several hours ago, but I don't know how to actually access my API now (api name geovalidate).

I go to [[IP ADDRESS]]/geovalidate in my browser, and I just get 502 Bad Gateway. I did drop the "hello" API; before when I went to [[IP ADDRESS]]/geovalidate I saw the "plumber is alive!" screen.

This may be a simple answer, thanks for the help!

This topic was automatically closed 42 days after the last reply. New replies are no longer allowed.

If you have a query related to it or one of the replies, start a new topic and refer back with a link.