[GH-ISSUE #173] Accessing Ambar interface #171

New issue

Closed

opened 2026-02-27 15:55:27 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 15:55:27 +03:00

Owner

Originally created by @musical10441 on GitHub (Jul 22, 2018).
Original GitHub issue: https://github.com/RD17/ambar/issues/173

I recently installed Ambar and am running into a problem:

When I access the Ambar web interface from my Ubantu server using localhost as the hostname all works fine; however, when I access the Ambar interface from another machine using the IP address (in this case a public IP address), the interface loads and after a few seconds, a message shows at the bottom " Oops, something went wrong".

Originally created by @musical10441 on GitHub (Jul 22, 2018). Original GitHub issue: https://github.com/RD17/ambar/issues/173 I recently installed Ambar and am running into a problem: When I access the Ambar web interface from my Ubantu server using localhost as the hostname all works fine; however, when I access the Ambar interface from another machine using the IP address (in this case a public IP address), the interface loads and after a few seconds, a message shows at the bottom " Oops, something went wrong".

kerem closed this issue

2026-02-27 15:55:27 +03:00

kerem commented

2026-02-27 15:55:28 +03:00

Author

Owner

@sochix commented on GitHub (Jul 22, 2018):

Check your firewall settings

вс, 22 июля 2018 г. в 14:14, musical10441 notifications@github.com:

I recently installed Ambar and am running into a problem:

When I access the Ambar web interface from my Ubantu server using
localhost as the hostname all works fine; however, when I access the Ambar
interface from another machine using the IP address (in this case a public
IP address), the interface loads and after a few seconds, a message shows
at the bottom " Oops, something went wrong".

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/RD17/ambar/issues/173, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABd-YmzinYi-Tfd2WYWj5mS94pNjLAFuks5uJF54gaJpZM4VZ9Pc
.

--
Best regards, Ilya (http://sochix.ru)
С уважением, Илья (http://sochix.ru)

@sochix commented on GitHub (Jul 22, 2018): Check your firewall settings вс, 22 июля 2018 г. в 14:14, musical10441 <notifications@github.com>: > I recently installed Ambar and am running into a problem: > > When I access the Ambar web interface from my Ubantu server using > localhost as the hostname all works fine; however, when I access the Ambar > interface from another machine using the IP address (in this case a public > IP address), the interface loads and after a few seconds, a message shows > at the bottom " Oops, something went wrong". > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/RD17/ambar/issues/173>, or mute the thread > <https://github.com/notifications/unsubscribe-auth/ABd-YmzinYi-Tfd2WYWj5mS94pNjLAFuks5uJF54gaJpZM4VZ9Pc> > . > -- Best regards, Ilya (http://sochix.ru) С уважением, Илья (http://sochix.ru)

kerem commented

2026-02-27 15:55:28 +03:00

Author

Owner

@musical10441 commented on GitHub (Jul 26, 2018):

Hi. I figured out the problem and it wasn't the firewall. Updating you in case others experience it.

In the Docker-Compose.yml file, under Frontend - the environment IP address to the API was set to a local network address (10.0.0.6:8080). That is accessible from within the local network, but not from externally.

To fix it, I had to use the PUBLIC ip address so that my remote machine can access the API (THANK YOU CHROME DEVELOPER TOOLS!).

I'm actually surprised that I have to expose the API to the public IP address. Most apps use it internal to the application but the Remote machine shouldn't ever need access to it.

Below is the section with the public IP address listed.

frontend:
depends_on:
webapi:
condition: service_healthy
image: ambar/ambar-frontend:latest
restart: always
networks:
- internal_network
ports:
- "80:80"
expose:
- "80"
environment:
- api=http://40.114.117.250:8080
pipeline0:
depends_on:
serviceapi:
condition: service_healthy
image: ambar/ambar-pipeline:latest
restart: always
networks:
- internal_network
environment:
- id=0
- api_url=http://serviceapi:8081
- rabbit_host=amqp://rabbit
filesystemcrawler:
depends_on:
serviceapi:
condition: service_healthy
image: ambar/ambar-local-crawler
restart: always
networks:
- internal_network
expose:
- "8082"
environment:
- name=filesystemcrawler
volumes:
- /home/dbr-admin/fileserver:/usr/data

@musical10441 commented on GitHub (Jul 26, 2018): Hi. I figured out the problem and it wasn't the firewall. Updating you in case others experience it. In the Docker-Compose.yml file, under Frontend - the environment IP address to the API was set to a local network address (10.0.0.6:8080). That is accessible from within the local network, but not from externally. To fix it, I had to use the PUBLIC ip address so that my remote machine can access the API (THANK YOU CHROME DEVELOPER TOOLS!). I'm actually surprised that I have to expose the API to the public IP address. Most apps use it internal to the application but the Remote machine shouldn't ever need access to it. Below is the section with the public IP address listed. frontend: depends_on: webapi: condition: service_healthy image: ambar/ambar-frontend:latest restart: always networks: - internal_network ports: - "80:80" expose: - "80" environment: - api=http://40.114.117.250:8080 pipeline0: depends_on: serviceapi: condition: service_healthy image: ambar/ambar-pipeline:latest restart: always networks: - internal_network environment: - id=0 - api_url=http://serviceapi:8081 - rabbit_host=amqp://rabbit filesystemcrawler: depends_on: serviceapi: condition: service_healthy image: ambar/ambar-local-crawler restart: always networks: - internal_network expose: - "8082" environment: - name=filesystemcrawler volumes: - /home/dbr-admin/fileserver:/usr/data