# Push Server Issue on vitalpbx- 3.2.5-2 installed on Google cloud  us-east-5  

**URL:** https://forums.vitalpbx.org/t/push-server-issue-on-vitalpbx-3-2-5-2-installed-on-google-cloud-us-east-5/3618
**Category:** VitalPBX
**Created:** [January 2, 2024, 2:40pm UTC](https://forums.vitalpbx.org/t/push-server-issue-on-vitalpbx-3-2-5-2-installed-on-google-cloud-us-east-5/3618 "2024-01-02T14:40:59Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![ahsan](https://forums.vitalpbx.org/letter_avatar_proxy/v4/letter/a/958977/32.png) [@ahsan](https://forums.vitalpbx.org/u/ahsan)
#### Post date: [January 2, 2024, 2:40pm UTC](https://forums.vitalpbx.org/t/push-server-issue-on-vitalpbx-3-2-5-2-installed-on-google-cloud-us-east-5/3618/1 "2024-01-02T14:40:59Z")

</div>

I have installed fresh vital pbx server with latest release 3.2.5-2 on google cloud us-east-5 everything is working fine except of push server. I did open all desired port for vital on google firewall as per vital requirement along with push server IP white listed on Vital server. The problem is when ever user registered his device and after some time registered user on push server shows offline that user . I tried with IOS and Android both devices and same issue happened.  
Note there is no other device active on same EXTENSION  
When i open vitalpbx app it updated my public ip and then i close app it registered on push and shows user status after some time it goes offline again

 ![Screen Shot 2024-01-01 at 4.22.05 AM](https://forums.vitalpbx.org/uploads/default/original/2X/6/6d7c33f1ae4b5855f98b8a9820f5a4ae08e42044.png)

---

<div class="post-metadata">

### Author: ![miguel](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/miguel/32/415_2.png) [@miguel](https://forums.vitalpbx.org/u/miguel)
#### Post date: [January 2, 2024, 3:55pm UTC](https://forums.vitalpbx.org/t/push-server-issue-on-vitalpbx-3-2-5-2-installed-on-google-cloud-us-east-5/3618/2 "2024-01-02T15:55:32Z")

</div>

Try using UDP instead of TLS. Or make sure that the port 5061 and 5063 are open in the Firewall.

---

<div class="post-metadata">

### Author: ![ahsan](https://forums.vitalpbx.org/letter_avatar_proxy/v4/letter/a/958977/32.png) [@ahsan](https://forums.vitalpbx.org/u/ahsan)
#### Post date: [January 2, 2024, 7:11pm UTC](https://forums.vitalpbx.org/t/push-server-issue-on-vitalpbx-3-2-5-2-installed-on-google-cloud-us-east-5/3618/3 "2024-01-02T19:11:36Z")

</div>

Thank you Miguel for your response, I opened both ports on firwall. Actually the problem that i am facing, my devices get register on push server and show status up but after some time it shows device unreachable

 ![Screen Shot 2024-01-03 at 12.24.32 AM](https://forums.vitalpbx.org/uploads/default/original/2X/3/3ed255ae8c8f89e4d0748b9d94eac1dadcaff33b.png)  
 ![Screen Shot 2024-01-03 at 2.32.57 PM](https://forums.vitalpbx.org/uploads/default/original/2X/4/49c6ed9a8cd8085fd721ae78a4c26fa0607374bc.png)

---

<div class="post-metadata">

### Author: ![ahsan](https://forums.vitalpbx.org/letter_avatar_proxy/v4/letter/a/958977/32.png) [@ahsan](https://forums.vitalpbx.org/u/ahsan)
#### Post date: [January 3, 2024, 9:42am UTC](https://forums.vitalpbx.org/t/push-server-issue-on-vitalpbx-3-2-5-2-installed-on-google-cloud-us-east-5/3618/4 "2024-01-03T09:42:55Z")

</div>

Same Asterisk server is working fine on another VPS hosting (Conatbo) server with current release of VITALPBX. The only difference is on google cloud this server is running behind NAT and i am fasing related push issue, i have attached both screen shots of device status (registerd user and then unreachable status )

---

<div class="post-metadata">

### Author: ![miguel](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/miguel/32/415_2.png) [@miguel](https://forums.vitalpbx.org/u/miguel)
#### Post date: [January 3, 2024, 5:47pm UTC](https://forums.vitalpbx.org/t/push-server-issue-on-vitalpbx-3-2-5-2-installed-on-google-cloud-us-east-5/3618/5 "2024-01-03T17:47:42Z")

</div>

Well, there must be something that you should configure on Google to make it work! Unfortunately, I don’t have that information. Maybe someone in the forum has some experience with it.

---

<div class="post-metadata">

### Author: ![ahsan](https://forums.vitalpbx.org/letter_avatar_proxy/v4/letter/a/958977/32.png) [@ahsan](https://forums.vitalpbx.org/u/ahsan)
#### Post date: [January 3, 2024, 5:54pm UTC](https://forums.vitalpbx.org/t/push-server-issue-on-vitalpbx-3-2-5-2-installed-on-google-cloud-us-east-5/3618/6 "2024-01-03T17:54:12Z")

</div>

I tried to find it but i could not find but i find your recommended guide for google deployment. I followed that guide but it is not working

---

<div class="post-metadata">

### Author: ![miguel](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/miguel/32/415_2.png) [@miguel](https://forums.vitalpbx.org/u/miguel)
#### Post date: [January 3, 2024, 6:05pm UTC](https://forums.vitalpbx.org/t/push-server-issue-on-vitalpbx-3-2-5-2-installed-on-google-cloud-us-east-5/3618/7 "2024-01-03T18:05:57Z")

</div>

The guide doesn’t cover anything related to push servers. This guide helps to install VitalPBX and to connect regular desktop devices.

---

<div class="post-metadata">

### Author: ![ahsan](https://forums.vitalpbx.org/letter_avatar_proxy/v4/letter/a/958977/32.png) [@ahsan](https://forums.vitalpbx.org/u/ahsan)
#### Post date: [January 3, 2024, 6:09pm UTC](https://forums.vitalpbx.org/t/push-server-issue-on-vitalpbx-3-2-5-2-installed-on-google-cloud-us-east-5/3618/8 "2024-01-03T18:09:35Z")

</div>

Yes i checked i dont know where is the problem is it based on google cloud the same vm with same spec are working well on cotabbo cloud and that vm is directly connected to internet

---

<div class="post-metadata">

### Author: ![system](https://forums.vitalpbx.org/uploads/default/original/1X/672b458a1d454755270c2c16adc5316b641c3c6a.png) [@system](https://forums.vitalpbx.org/u/system)
#### Post date: [February 2, 2024, 6:09pm UTC](https://forums.vitalpbx.org/t/push-server-issue-on-vitalpbx-3-2-5-2-installed-on-google-cloud-us-east-5/3618/9 "2024-02-02T18:09:42Z")

</div>

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