Build Auto Localization Error

Summary

Build Auto Localization Error : Failed to connect to server

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Other

Steps to Reproduce

  1. Build > Export Localization
  2. Build > Build Auto Localization

Expected Result

When the translation process has finished I will be prompted to import the result.

Observed Result

It had be prompted “Failed to connect to server”

Platform(s)

windows

Additional Notes

I’ve been using it fine until now, but this problem started occurring yesterday.
I didn’t manually edit any localization files.
The log is as follows.


[2025.02.14-04.49.06:831][464]LogValkyrieAutoLocalization: [대기중] 자동 현지화 - 초기화 중…
[2025.02.14-04.49.07:359][476]LogValkyrieAutoLocalization: [대기중] 자동 현지화 - 현지화 작업 재개 중…
[2025.02.14-04.49.07:359][476]LogValkyrieAutoLocalization: [대기중] 자동 현지화 - 현지화 작업 채택 중…
[2025.02.14-04.49.07:359][476]LogValkyrieAutoLocalization: [대기중] 자동 현지화 - 현지화 작업 생성 중…
[2025.02.14-04.49.40:530][150]LogHttp: Warning: Retry 1 on https://content-service.bfda.live.use1a.on.epicgames.com/api/content/v3/module/80aec74b-457e-f0e0-6e8d-898c2c14c676/localization
[2025.02.14-04.50.16:689][258]LogHttp: Warning: Retry 2 on https://content-service.bfda.live.use1a.on.epicgames.com/api/content/v3/module/80aec74b-457e-f0e0-6e8d-898c2c14c676/localization
[2025.02.14-04.50.58:895][385]LogHttp: Warning: Retry 3 on https://content-service.bfda.live.use1a.on.epicgames.com/api/content/v3/module/80aec74b-457e-f0e0-6e8d-898c2c14c676/localization
[2025.02.14-04.51.46:552][528]LogHttp: Warning: Retry 4 on https://content-service.bfda.live.use1a.on.epicgames.com/api/content/v3/module/80aec74b-457e-f0e0-6e8d-898c2c14c676/localization
[2025.02.14-04.51.51:151][541]LogEOSSDK: LogEOS: Updating Product SDK Config, Time: 308.720795
[2025.02.14-04.51.53:154][547]LogEOSSDK: LogEOS: SDK Config Product Update Request Completed - No Change
[2025.02.14-04.51.53:154][547]LogEOSSDK: LogEOS: ScheduleNextSDKConfigDataUpdate - Time: 310.056396, Update Interval: 329.698792
[2025.02.14-04.52.04:826][582]LogEOSSDK: LogEOS: Updating Product SDK Config, Time: 341.282562
[2025.02.14-04.52.06:829][588]LogEOSSDK: LogEOS: SDK Config Product Update Request Completed - No Change
[2025.02.14-04.52.06:829][588]LogEOSSDK: LogEOS: ScheduleNextSDKConfigDataUpdate - Time: 342.618439, Update Interval: 308.598907
[2025.02.14-04.53.01:653][753]LogHttp: Warning: Retry 5 on https://content-service.bfda.live.use1a.on.epicgames.com/api/content/v3/module/80aec74b-457e-f0e0-6e8d-898c2c14c676/localization
[2025.02.14-04.53.31:889][843]LogHttp: Warning: HttpRetry: Resetting log verbosity to Warning due to requests being retried
[2025.02.14-04.53.31:889][843]LogOnline: Warning: OSS: Http Unexpected Result: HttpResult: 0 Code: 0 Error: Failure ErrorCode=errors.com.epicgames.online.generic.connection_failure, Message=서버에 연결하지 못했습니다., Raw=connection_failure
[2025.02.14-04.53.31:890][843]LogValkyrieAutoLocalization: Error: [실패] 자동 현지화 - 서버에 연결하지 못했습니다.
[2025.02.14-04.56.56:461][630]LogEOSSDK: LogEOSPresence: Updating Presence to Online. LocalUserId=[e68…cd4] RichText=
[2025.02.14-04.56.57:128][632]LogEOSSDK: Warning: LogEOS: FEpicGamesPlatform::GetOnlinePlatformType - unable to map None to EOS_OnlinePlatformType
[2025.02.14-04.57.17:470][693]LogEOSSDK: LogEOS: Updating Product SDK Config, Time: 653.927185
[2025.02.14-04.57.19:470][699]LogEOSSDK: LogEOS: SDK Config Product Update Request Completed - No Change
[2025.02.14-04.57.19:470][699]LogEOSSDK: LogEOS: ScheduleNextSDKConfigDataUpdate - Time: 655.260315, Update Interval: 342.584320
[2025.02.14-04.57.26:473][720]LogEOSSDK: LogEOS: Updating Product SDK Config, Time: 644.042542
[2025.02.14-04.57.28:475][726]LogEOSSDK: LogEOS: SDK Config Product Update Request Completed - No Change
[2025.02.14-04.57.28:475][726]LogEOSSDK: LogEOS: ScheduleNextSDKConfigDataUpdate - Time: 645.377014, Update Interval: 333.556946
[2025.02.14-05.03.07:795][857]LogEOSSDK: LogEOS: Updating Product SDK Config, Time: 985.364075
[2025.02.14-05.03.08:798][860]LogEOSSDK: LogEOS: Updating Product SDK Config, Time: 1005.254272
[2025.02.14-05.03.09:798][863]LogEOSSDK: LogEOS: SDK Config Product Update Request Completed - No Change
[2025.02.14-05.03.09:798][863]LogEOSSDK: LogEOS: ScheduleNextSDKConfigDataUpdate - Time: 986.699585, Update Interval: 338.103577
[2025.02.14-05.03.10:800][866]LogEOSSDK: LogEOS: SDK Config Product Update Request Completed - No Change
[2025.02.14-05.03.10:800][866]LogEOSSDK: LogEOS: ScheduleNextSDKConfigDataUpdate - Time: 1006.589355, Update Interval: 346.488220

hi,


  
  "errorCode": "errors.com.epicgames.content-service.auth_required",
  "errorMessage": "No authorization header."

There appears to be some sort of error trying to login to server
click on the highlight blue link and enter your login derails.
You may need to clear browser cache first.

Im confused, where is this error from? I don’t see it in the logs they posted

hi ,
it’s a common server response to

UEFN - Content Service

You have to log on to the above screen or you will get a reply from the server as an error above.

Once logged in details are stored in the browser cache.

There could then be other errors, but need to login locally first

Were you trying to access this link? if yes it would give you an authentication error since only people with permissions to the project should be able to access that data.

I tried it myself on a project I have access to and got the same error I believe.

When going to that page I expected an error but that page just says this:

there is the report
FORT-815612 is ‘Closed’ as ‘Fixed’. The issue will be addressed in 34.10.

Build Auto Localization failing - General / Issues and Bug Reporting - Epic Developer Community Forums

Fortnite Documentation Text Localization in Unreal Editor for Fortnite

There are many bug reports that have been closed as Duplicate known problem

finally, there is the report
FORT-815612 is ‘Closed’ as ‘Fixed’. The issue will be addressed in 34.10.

Build Auto Localization failing - General / Issues and Bug Reporting - Epic Developer Community Forums

1 Like

(post deleted by author)

Thanks for your answer.
I’ll wait and hope it gets fixed in version 34.10.

1 Like