Replies: 2 comments
-
|
@IsaacYangSLA can you help answer this question about CNAME record vs A record, thanks |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
ChatGPT
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Python version (
python3 -V)3.12
NVFlare version (
python3 -m pip list | grep "nvflare")2.5.2
NVFlare branch (if running examples, please use the branch that corresponds to the NVFlare version,
git branch)No response
Operating system
MacOS + Amazon Linux 2023
Have you successfully run any of the following examples?
Please describe your question
I tried to test a real-world scenario using NVFlare where a client runs in my MacOS and the server runs in an AWS EC2 instance. Below are the steps I followed:
a.b.c.d).nvflare.mydomain.com) toa.b.c.d.nc -l 0.0.0.0 8002on the server andnc nvflare.mydomain.com:8002on the client, and everything seemed ok.nvflare.mydomain.comin theproject.yml, provisioned, transferred files, and started the server and client.After trying different things, I redid step 2 and this time created a CNAME record from
nvflare.mydomain.comtoec2-a-b-c-d.us-east-2.compute.amazonaws.com.This solved the problem and I can now have
nvflare.mydomain.comin myproject.yml.Can someone explain why having the A record did not work in this case?
Beta Was this translation helpful? Give feedback.
All reactions