Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

The cipher AES128-GCM-SHA256 is not supported for TLSv1.2.

Open
  • Is something wrong?
#415 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
api, backend

Research direction

Start with the request path in APIRequest.java and the AdAccount.java call shown in the stack trace, then reproduce the v16.0 request in the reported CentOS 7.9 environment. Check how the Java SDK negotiates TLSv1.2 and the AES128-GCM-SHA256 cipher. Done means the logged API request completes without the cipher error.

Written by the indexing model from the issue text.

Description

Which SDK version are you using?

v16.0.0

What's the issue?

return msg: {"error":{"message":"The cipher AES128-GCM-SHA256 is not supported for TLSv1.2.","type":"GraphInsecureException","code":8,"fbtrace_id":"A8N-tgfyh73UaZ6B-iLuMTf"}}

Steps/Sample code to reproduce the issue

Linux env:

LSB Version:    :core-4.1-amd64:core-4.1-noarch
Distributor ID: CentOS
Description:    CentOS Linux release 7.9.2009 (Core)
Release:        7.9.2009
Codename:       Core

request log:

2023-03-02 14:43:56.344 [pool-1-thread-4] INFO  com.pw.ad.api.facebook.FbApiSdk - Facebook API Context Stdout Log: ========Start of API Call========
2023-03-02 14:43:56.344 [pool-1-thread-4] INFO  com.pw.ad.api.facebook.FbApiSdk - Facebook API Context Stdout Log: Request:
2023-03-02 14:43:56.345 [pool-1-thread-4] INFO  com.pw.ad.api.facebook.FbApiSdk - Facebook API Context Stdout Log: GET: https://graph.facebook.com/v16.0/act_<ignore actual account_id>/advideos?limit=3&access_token=...ignore actual access token...
2023-03-02 14:43:56.523 [pool-1-thread-4] ERROR com.powerwin.center.commons.filter.DubboProviderFilter - error={"error":{"message":"The cipher AES128-GCM-SHA256 is not supported for TLSv1.2.","type":"G
raphInsecureException","code":8,"fbtrace_id":"A8N-tgfyh73UaZ6B-iLuMTf"}}
com.facebook.ads.sdk.APIException$FailedRequestException: {"error":{"message":"The cipher AES128-GCM-SHA256 is not supported for TLSv1.2.","type":"GraphInsecureException","code":8,"fbtrace_id":"A8N-tgfyh73UaZ6B-iLuMTf"}}
        at com.facebook.ads.sdk.APIRequest.readResponse(APIRequest.java:313)
        at com.facebook.ads.sdk.APIRequest.access$100(APIRequest.java:54)
        at com.facebook.ads.sdk.APIRequest$DefaultRequestExecutor.sendGet(APIRequest.java:539)
        at com.facebook.ads.sdk.APIRequest$DefaultRequestExecutor.execute(APIRequest.java:523)
        at com.facebook.ads.sdk.APIRequest.executeInternal(APIRequest.java:199)
        at com.facebook.ads.sdk.AdAccount$APIRequestGetAdVideos.execute(AdAccount.java:10471)
        at com.facebook.ads.sdk.AdAccount$APIRequestGetAdVideos.execute(AdAccount.java:10466)
Observed Results:
  • What happened? This could be a description, log output, etc.
Expected Results:
  • What did you expect to happen?
Dominant language
Java
Stars
473
Forks
344
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from facebook/facebook-java-business-sdk

All issues in facebook/facebook-java-business-sdk

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.