728x90

FCM ports and your firewall

If your organization has a firewall to restrict traffic to or from the Internet, you need to configure it to allow mobile devices to connect with FCM in order for devices on your network to receive messages. FCM typically uses port 5228, but it sometimes uses 443, 5229, and 5230.

For devices connecting on your network, FCM doesn't provide specific IPs because our IP range changes too frequently and your firewall rules could get out of date, impacting your users' experience. Ideally, allowlist ports 5228-5230 & 443 with no IP restrictions. However, if you must have an IP restriction, you should allowlist all of the IP addresses listed in goog.json. This large list is updated regularly, and you are recommended to update your rules on a monthly basis. Problems caused by firewall IP restrictions are often intermittent and difficult to diagnose.

We do offer a set of domain names that can be allowlisted instead of IP addresses. Those hostnames are listed below. If we start using additional hostnames, we will update the list here. Using domain names for your firewall rule may or may not be functional in your firewall device.

TCP ports to open:

  • 5228
  • 5229
  • 5230
  • 443

Hostnames to open:

  • mtalk.google.com
  • mtalk4.google.com
  • mtalk-staging.google.com
  • mtalk-dev.google.com
  • alt1-mtalk.google.com
  • alt2-mtalk.google.com
  • alt3-mtalk.google.com
  • alt4-mtalk.google.com
  • alt5-mtalk.google.com
  • alt6-mtalk.google.com
  • alt7-mtalk.google.com
  • alt8-mtalk.google.com
  • android.apis.google.com
  • device-provisioning.googleapis.com
  • firebaseinstallations.googleapis.com

Network Address Translation and/or Stateful Packet Inspection firewalls:

If your network implements Network Address Translation (NAT) or Stateful Packet Inspection (SPI), implement a 30 minute or larger timeout for our connections over ports 5228-5230. This enables us to provide reliable connectivity while reducing the battery consumption of your users' mobile devices.

 

In normally, Do not define especially hostname without ports. 

 

'Java' 카테고리의 다른 글

[Moyamo] EMMA with Aurora RDS 8.0  (0) 2025.07.27
Method: projects.messages.send  (1) 2024.10.01
MyBatis Mapper Setting  (0) 2024.09.24
Class Verify  (0) 2024.09.23
Java - Json 과 Gson 이란?  (0) 2024.09.23
728x90

https://mybatis.org/mybatis-3/ko/configuration.html

 

mybatis – 마이바티스 3 | 매퍼 설정

매퍼 설정 마이바티스 XML 설정파일은 다양한 설정과 프로퍼티를 가진다. 문서의 구조는 다음과 같다.: configuration properties 이 설정은 외부에 옮길 수 있다. 자바 프로퍼티 파일 인스턴스에 설정할

mybatis.org

 

https://jaeano.tistory.com/entry/Spring-Boot-Repository-MyBatis-Mapper-Domain

 

[Spring Boot] Repository Component (MyBatis, @Mapper, Insert, Domain)

이번에는 Spring MVC Architecture의 Model 부분과 관련된 Repository에 대해 알아 볼 것이다. 그 동안 모든 Component는 특정 어노테이션을 통해 IoC 컨테이너에 Bean으로 등록하고 어떤 Layer에서 사용 될 지 가

jaeano.tistory.com

 

'Java' 카테고리의 다른 글

Method: projects.messages.send  (1) 2024.10.01
FCM HTTP v1 Firewall Port bound  (4) 2024.09.30
Class Verify  (0) 2024.09.23
Java - Json 과 Gson 이란?  (0) 2024.09.23
[Spring Security] HTTP Basic Auth  (0) 2024.09.23
728x90

https://guava.dev/releases/21.0/api/docs/index.html?com/google/common/base/Verify.html

'Java' 카테고리의 다른 글

FCM HTTP v1 Firewall Port bound  (4) 2024.09.30
MyBatis Mapper Setting  (0) 2024.09.24
Java - Json 과 Gson 이란?  (0) 2024.09.23
[Spring Security] HTTP Basic Auth  (0) 2024.09.23
How to set up Multi Module project  (0) 2024.09.19
728x90

https://galid1.tistory.com/501

 

Java - Json 과 Gson 이란?

Json과 Gson JSON을 사용하기전에 당연히 여러곳에서 무엇인지를 검색한 뒤에 사용했지만 역시 설명하려고 하면 버벅거리게 되는것 같습니다. 아무래도 정확히 알지 못해서인것 같습니다. 때문에

galid1.tistory.com

 

 

'Java' 카테고리의 다른 글

MyBatis Mapper Setting  (0) 2024.09.24
Class Verify  (0) 2024.09.23
[Spring Security] HTTP Basic Auth  (0) 2024.09.23
How to set up Multi Module project  (0) 2024.09.19
Improved Java Logging with Mapped Diagnostic Context (MDC)  (1) 2024.09.12

+ Recent posts