I have Ubuntu 18.04 where I run nvim as a server: nvim --listen <ip>:<port> --headless.
And MacOS Catalina where I run neovim-qt as a client: nvim-qt --server <IP>:<port>.
The top and bottom lines are presented incorrectly:

However, when I run neovim-qt locally they are fine.
Ubuntu:

MacOS:

Both machines have the same .vimrc and ginit.vim:
"I want to see buffers on top of the screen
GuiTabline 0
"This is a good feature but unfortunately it is not good for the YCM
"Need to check from time to time if it works
GuiPopupmenu 0
Guifont Source Code Pro for Powerline:h16
colorscheme monokai
"Allows yanking to the local clipboard(even from remote!)
call GuiClipboard()
I went through help: nvim-gui-shim but did not find a command fixing the problem.
Could you please advise?
What is the output of :GuiFont?
It probably displays something other than Source Code Pro for Powerline:h16.
You need to escape the spaces, same as guifont:
Guifont Source\ Code\ Pro\ for\ Powerline:h16
Would you like to expand the documentation to include a note about this and an example?
I have seen this before and I think it would be useful to other users :)
@jgehrig ,
Actually, :GuiFont returns the font defined in ginit.vim so I am not sure if it is reasonable to update the documentation.
Nevertheless, I've added the escape symbols but it did not help.
Sorry, I think I was confused as to what the issue was... What exactly is the problem?
Is this an issue with the coloring of the arrow-like vim-airline characters?
Notice the highlighted characters are white, not yellow:

@jgehrig , the problem is that the highlighted characters are rendered differently when neovim-qt running at MacOS is connected to nvim running at Ubuntu and when neovim-qt is connected to a local nvim(for both MacOS and Ubuntu).
Perhaps it's because the termguicolors configuration for the remote nvim isn't working.
I had a similar problem with goneovim because I didn't set termguicolors at startup (See https://github.com/akiyosi/goneovim/issues/79#issuecomment-611001053).
@akiyosi , adding set termguicolors to init.vim did solve the problem!
Thank you very much!
Most helpful comment
Perhaps it's because the termguicolors configuration for the remote nvim isn't working.
I had a similar problem with goneovim because I didn't set termguicolors at startup (See https://github.com/akiyosi/goneovim/issues/79#issuecomment-611001053).