QASK.org

How to setup Multipass VM on Mac and integrate with Vscode to run Linux virtually: I recently mailed my TA on how to setup Linux on a Mac for a Computer Systems course to which I received the steps highlighted below- (I am stuck in the 6th and 7th step)
I have some idea of what is happening like Multipass is used to create a virtual machine that runs on a server and there's no GUI. Also, I understand that ssh will be used to login into the VM. But, I don't understand why do I have to edit the public key in the instance.
(You can go through the email and I have highlighted the exact problem I am facing below the email.)

---

*

Install Mutipass through:
brew install --cask multipass

*

Find a suitable instance(22.04LTS proffered) and create an instance in Multipass:
first run multipass find and look for the 22.04 LTS instance.

After that, run multipass launch jammy Note here that jammy is the name used to create 22.04LTS instance.

*

Generate SSH Key Pair on MacBook:
Run the ssh-keygen command in your terminal. This will generate a pair of keys; one public (the one you'll share) and one private (the one you keep secure on your device). When you run the command, you'll be prompted to enter a file to save the key, just press enter to save it in the default location, which is usually ~/.ssh/id_rsa.

*

Get a List of Running Instances:
Run multipass list to get a list of all your running virtual machine instances.

*

Select and Access the Instance:
Note the name of your instance (e.g., 'brimming-yak'). Access the shell for your instance by running multipass shell brimming-yak.

6. Edit the authorized_keys File in VM:
Inside the shell, navigate to the ~/.ssh/ directory. If it doesn't exist, create it using mkdir ~/.ssh. Use a text editor like nano or vim to edit the authorized_keys file. If it doesn't exist, you can create it with touch ~/.ssh/authorized_keys. Open it in the editor and append your public key (the contents of ~/.ssh/id_rsa.pub on your MacBook) to this file.

*

Restart the Instance:
Exit the shell and restart the instance with multipass restart brimming-yak.

*

Get the IP Address of the Instance:
Use multipass info brimming-yak to get detailed information about the instance, including its IP address.

*

SSH into the Machine:
You can now SSH into the machine from your MacBook terminal using ssh ubuntu@[IP Address of Instance]. Replace [IP Address of Instance] with the actual IP address you got from the previous step.

*

Set Up VSCode for SSH:
Install the "Visual Studio Code Remote - SSH" extension in VSCode.
Click on the green box in the lower-left corner of VSCode, then select Remote-SSH: Connect to Host..., and enter ubuntu@[IP Address of Instance]. VSCode will now set up a connection, and you'll be able to use VSCode as if you were working directly on the VM.
For detailed instructions, you can refer to the official VSCode documentation.

---

Now, whenever I try the step7 I get the error- restart failed: ssh failed to authenticate: 'Access denied for 'publickey'. Authentication that can continue: publickey'

I have looked up numerous web articles to try and fix this problem with no success. Is there anything wrong with the steps highlighted that is causing this problem.

Thanks for any help! :)

How to setup Multipass VM on Mac and integrate with Vscode to run Linux virtually I recently mailed my TA on how to setup Linux on a Mac for a Computer Systems course to which I received the steps highlighted below- (I am stuck in -

Diagnosing / Troubleshooting SMB mount: Ubuntu 22.04: A Synology NAS SMB mount tested good with a Mac. A list of Samba share returned by MacOS Finder:

I would like to mount the SMB share:
sudo mount -t cifs //192.168.8.109/home -o username=****,password=****** /home/user/NAS_mount

however, an error is returned:
mount error(13): Permission denied

What is the starting point / questions / diagnostic to understand / resolve the error?

Diagnosing / Troubleshooting SMB mount Ubuntu 22.04: A Synology NAS SMB mount tested good with a Mac. A list of Samba share returned by MacOS Finder: I would like to mount the SMB shar - 1 answer

How can I fix my vulkan, why does my vulkaninfo fail?: If I run vulkaninfo I get a seg fault (though I can't find the core dump):
$ vulkaninfo
WARNING: [Loader Message] Code 0 : loader_scanned_icd_add: Driver /usr/lib/x86_64-linux-gnu/libvulkan_nouveau.so supports Vulkan 1.3, but only supports loader interface version 4. Interface version 5 or newer required to support this version of Vulkan (Policy )
WARNING: [Loader Message] Code 0 : terminator_CreateInstance: Failed to CreateInstance in ICD 4. Skipping ICD.
Segmentation fault (core dumped)

However, I can run it like this:
$ VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.x86_64.json:/usr/share/vulkan/icd.d/radeon_icd.i686.json vulkaninfo

and it gives expected output, eg if I send it through | grep driver:
MESA: error: Use of VkSurfacePresentModeCompatibilityEXT without a VkSurfacePresentModeEXT set. This is an application bug.
driverVersion = 23.3.1 (96481281)
driverID = DRIVER_ID_MESA_RADV
driverName = radv
driverInfo = Mesa 23.3~git2309020600.1ae3c4~oibaf~l (git-1ae3c40 2023-09-02 lunar-oibaf-ppa)
driverUUID = 414d442d-4d45-5341-2d44-525600000000
driverUUID = 414d442d-4d45-5341-2d44-525600000000
driverID = DRIVER_ID_MESA_RADV
driverName = radv
driverInfo = Mesa 23.3~git2309020600.1ae3c4~oibaf~l (git-1ae3c40 2023-09-02 lunar-oibaf-ppa)
VK_KHR_driver_properties : extension revision 1

My graphics use AMDGPU driver:
$ inxi -G
Graphics:
Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
driver: amdgpu v: kernel
Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.8 driver: X:
loaded: amdgpu unloaded: modesetting dri: radeonsi gpu: amdgpu
resolution: 1920x1080~75Hz
API: OpenGL v: 4.6 Mesa 23.3~git2309020600.1ae3c4~oibaf~l (git-1ae3c40
2023-09-02 lunar-oibaf-ppa) renderer: AMD Radeon RX 580 Series (polaris10
LLVM 15.0.7 DRM 3.49 6.2.0-31-generic)

Is the problem that the oibaf drivers (bleeding edge) are including files I don't want, or is something else going on? This all relates to debugging Steam, most of of my games have stopped launching (CS:GO in particular, not yet updated to CS:GO 2).
$ dpkg -S libvulkan_nouveau.so
$ dpkg -L mesa-vulkan-drivers

Show that all of the /usr/share/vulkan/icd.d/*_icd.x86_64.json and /usr/lib/x86_64-linux-gnu/libvulkan_*.so files comes from mesa-vulkan-drivers.

Example game launch for Dyson Sphere Program:
/bin/sh\0-c\0/home/pbhj/.steam/debian-installation/ubuntu12_32/reaper SteamLaunch AppId=1366540 -- /home/pbhj/.steam/debian-installation/ubuntu12_32/steam-launch-wrapper -- '/media/WDblue2TBmedia/games/steamapps/common/SteamLinuxRuntime_sniper'/_v2-entry-point --verb=waitforexitandrun -- '/home/pbhj/.steam/debian-installation/steamapps/common/Proton - Experimental'/proton waitforexitandrun '/media/WDblue2TBmedia/games/steamapps/common/Dyson Sphere Program/DSPGAME.exe'\0
chdir "/media/WDblue2TBmedia/games/steamapps/common/Dyson Sphere Program"
ERROR: ld.so: object '/home/pbhj/.steam/debian-installation/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/pbhj/.steam/debian-installation/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/pbhj/.steam/debian-installation/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/pbhj/.steam/debian-installation/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/pbhj/.steam/debian-installation/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.

(process:8427): steam-runtime-tools-CRITICAL **: 00:06:02.354: _srt_constructor: assertion '_srt_check_not_setuid ()' failed
pressure-vessel-wrap[8427]: E: Cannot run /usr/bin/bwrap: wait status 256
pressure-vessel-wrap[8427]: E: Diagnostic output:
bwrap: setting up uid map: Permission denied

pressure-vessel-wrap[8427]: E: Cannot run /media/WDblue2TBmedia/games/steamapps/common/SteamLinuxRuntime_sniper/pressure-vessel/bin/pv-bwrap: wait status 256
pressure-vessel-wrap[8427]: E: Diagnostic output:
bwrap: setting up uid map: Permission denied

Uploaded AppInterfaceStats to Steam

How can I fix my vulkan, why does my vulkaninfo fail? If I run vulkaninfo I get a seg fault (though I can't find the core dump): $ vulkaninfo WARNING: [Loader Message] Code 0 : loader_scanned_icd_add: -

Obsidian.md's "end-to-end" encryption & privacy: Obsidian.md claims

End-to-end encryption means that the data is encrypted from the moment it leaves your device, and can only be decrypted using your encryption key once it's back on one of your devices.

We can't read your data. Neither can any potential eavesdroppers, such as your internet service provider.

In the rare case of a complete server breach, your data remains encrypted—no one can decrypt your files without knowing your password.

However as per their blog article, symmetric encryption AES-256-GCM is used, with a key hash derived from the user's password / salt using scrypt, and two recent alternative server implementations [4] [5] show that the derived key hash is transmitted to the Obsidian's servers by the app during vault creation (among a few other calls), and stored in their database.

So if a symmetric encryption algorithm is used, and both the end-user user and Obsidian's server know the symmetric key, how come they wouldn't be able to decrypt the data?

Obsidian.md's "end-to-end" encryption & privacy Obsidian.md claims End-to-end encryption means that the data is encrypted from the moment it leaves your device, and can only be decrypted using yo -

iwlwifi ubuntu drivers upgrade: I'm trying to use the Intel AX211 on Ubuntu 20.04 with the latest drivers. However, when I copy the latest drivers for this chip to /lib/firmware, I consistently receive the following message:
[ 144.790109] iwlwifi 0000:00:14.3: base HW address: b0:dc:ef:a3:c0:9b

[ 144.811610] iwlwifi 0000:00:14.3 wlo1: renamed from wlan0
[ 555.354495] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-66.ucode failed with error -2
[ 555.354507] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-65.ucode failed with error -2
[ 555.354802] iwlwifi 0000:00:14.3: api flags index 2 larger than supported by driver
[ 555.354814] iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.25
[ 555.355115] iwlwifi 0000:00:14.3: loaded firmware version 64.97bbee0a.0 so-a0-gf-a0-64.ucode op_mode iwlmvm
[ 555.385082] iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6E AX211 160MHz, REV=0x370
[ 555.535079] iwlwifi 0000:00:14.3: loaded PNVM version 0x5a8dfca
[ 555.547617] iwlwifi 0000:00:14.3: Detected RF GF, rfid=0x2010d000
[ 555.617023] iwlwifi 0000:00:14.3: base HW address: b0:dc:ef:a3:c0:9b
[ 555.637339] iwlwifi 0000:00:14.3 wlo1: renamed from wlan0

First question: why this version 66 doesn't exist at https://github.com/endlessm/linux-firmware. Also, I can't seem to force it to use a newer version with a higher number (7x). To test this, I executed mv iwlwifi-so-a0-gf* _old/ and copied the file from the repository. But then, I received the following notifications:
[ 639.807608] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-66.ucode failed with error -2
[ 639.807617] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-65.ucode failed with error -2
[ 639.807629] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-64.ucode failed with error -2
[ 639.807637] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-63.ucode failed with error -2
[ 639.807644] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-62.ucode failed with error -2
[ 639.807653] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-61.ucode failed with error -2
[ 639.807660] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-60.ucode failed with error -2
[ 639.807668] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-59.ucode failed with error -2
[ 639.807674] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-58.ucode failed with error -2
[ 639.807681] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-57.ucode failed with error -2
[ 639.807689] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-56.ucode failed with error -2
[ 639.807695] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-55.ucode failed with error -2
[ 639.807702] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-54.ucode failed with error -2
[ 639.807710] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-53.ucode failed with error -2
[ 639.807716] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-52.ucode failed with error -2
[ 639.807723] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-51.ucode failed with error -2
[ 639.807728] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-50.ucode failed with error -2
[ 639.807735] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-49.ucode failed with error -2
[ 639.807742] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-48.ucode failed with error -2
[ 639.807748] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-47.ucode failed with error -2
[ 639.807755] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-46.ucode failed with error -2
[ 639.807773] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-45.ucode failed with error -2
[ 639.807780] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-44.ucode failed with error -2
[ 639.807787] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-43.ucode failed with error -2
[ 639.807794] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-42.ucode failed with error -2
[ 639.807801] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-41.ucode failed with error -2
[ 639.807807] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-40.ucode failed with error -2
[ 639.807814] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-39.ucode failed with error -2
[ 639.807815] iwlwifi 0000:00:14.3: no suitable firmware found!
[ 639.807817] iwlwifi 0000:00:14.3: minimum version required: iwlwifi-so-a0-gf-a0-39
[ 639.807819] iwlwifi 0000:00:14.3: maximum version supported: iwlwifi-so-a0-gf-a0-66
[ 639.807819] iwlwifi 0000:00:14.3: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

I'm wondering how I can force the loading of these newer drivers (e.g., iwlwifi-so-a00-gf-a0-7x), either by increasing the maximum version supported or through some other method.

iwlwifi ubuntu drivers upgrade I'm trying to use the Intel AX211 on Ubuntu 20.04 with the latest drivers. However, when I copy the latest drivers for this chip to /lib/firmware, I -

can't embed Rumble videos in oEmbed providers module: I've got oEmbed providers installed on two sites and recently wanted to add rumble to the list of providers. I've created a new provider bucket and included rumble but if I try and add a rumble URL or embed URL it gives me an:

"InvalidArgumentException: Unknown provider 'Rumble.com' in Drupal\oembed_providers\OEmbed\ProviderRepositoryDecorator->get() (line 217 of modules/contrib/oembed_providers/src/OEmbed/ProviderRepositoryDecorator.php)".

I've come to understand that the provider name has to be exact. Within the OEMBED Providers json file the rumble info looks like this:
{
"provider_name": "Rumble",
"provider_url": "https://rumble.com/",
"endpoints": [
{
"url": "https://rumble.com/api/Media/oembed.{format}",
"discovery": true
}
]
},

notice the provider_name is "Rumble".

If I go to iframely.com and paste in a rumble URL I will see, under the oEmbed tab, that the provider name is Rumble.com. I tried to create a custom provider called Rumble.com but the machine name reverts to rumble_com so it doesn't work.

I've looked for the answer to this all over the internet and I can't seem to figure it out. Any help would be greatly appreciated.

can't embed Rumble videos in oEmbed providers module I've got oEmbed providers installed on two sites and recently wanted to add rumble to the list of providers. I've created a new provider bucket and -

Need to see boot/system log from before actual session because of system shutdown after 30 minutes, only actual session log can be viewed: Laptop is an Acer Aspire V3-772 with 8GB and Ubuntu 22.04.3 LTS, Gnome 42.9 & Wayland on UEFI. The memtest could only pass once (without errors) because the laptop always crashes after close to 30 minutes. I am not sure of the integrity of the memory this way.

Because of a probable hardware problem in my friends laptop (always shutting off after half an hour), I wanted to take a look at the log from before the crash, but I can only acces the log from the actual session that is being worked at. Journalctl only shows this session and also the log viewer has no other logs than the actual session. Listing the log directory just shows 1 log.

I did read about the configuration for journalctl and did make the change from auto to persistent in that conf., but nothing changed.

B.t.w. As the shutdown also happened during memtest from Grub, I suspect the problem is not in the Ubuntu OS, because that is not loaded at that moment. Would it still be possible that a hardware failure could be revealed from a Ubuntu log?

I already ordered a new memory strip to switch with the memory in the laptop to see if that changes anything.

Power is ok, battery is full, temperature is not the problem, so looking at the logs seems to me the only way to find out what is the case.

Need to see boot/system log from before actual session because of system shutdown after 30 minutes, only actual session log can be viewed Laptop is an Acer Aspire V3-772 with 8GB and Ubuntu 22.04.3 LTS, Gnome 42.9 & Wayland on UEFI. The memtest could only pass once (without errors) - 1 answer

Grsync does not finish transfer (stuck): A directory with files is to be moved to a NAS. For some reason it becomes stuck in the sense that the upper progress bar indicates 100%, though global progress remains at 90%:

I removed .lnk files in the payload. That helped somewhat, but now it is stuck elsewhere. I think that grsync was endlessly traversing the directory in the sym-link?

Is there another file type similar to .lnk that is causing a "recursive" problem?

Grsync does not finish transfer (stuck) A directory with files is to be moved to a NAS. For some reason it becomes stuck in the sense that the upper progress bar indicates 100%, though -

How do i change these panel settings in Kubuntu (see attached image). Is it possible?: So i want to

* Change the icon size of the window tab icon.

* Change the width of the window tab.

* Disable panel-pinning completely.

Is this possible?

Thanks in advance

How do i change these panel settings in Kubuntu (see attached image). Is it possible? So i want to Change the icon size of the window tab icon. Change the width of the window tab. Disable panel-pinning completely. Is this possible? -

Proxmox port forwarding to Container behind NAT: We have recently bought a server from the Hetzner server auction and want to migrate our previous root server.
Previously we used only windows server, but now we want to set it up a bit more modular with proxmox.

We have a single public IP address, so we chose to use NAT with a 10.0.0.0/24 internal subnet.

The containers can access the internet, so this works fine.

But we can't connect to servers which run inside the containers over custom ports.

How can I properly forward the ports? We tried the routing and port forwarding as listed below. Something went wrong, the ports arent open, as shown by portscans.
There is currently only a firewall in the Proxmox host, the server host firewall is disabled, so I dont know why traffic should be blocked.

This is the current setup of the proxmox network interface:
auto lo
iface lo inet loopback

iface lo inet6 loopback

auto eno1
iface eno1 inet static
address public.ipv4/26
gateway public.gateway
up route add -net public.ipv4 netmask 255.255.255.192 gw public.ipv4 dev eno1
# route public.ipv4.range.start/26 via public.ipv4.range.start+1

iface eno1 inet6 static
address public.ipv6/128
gateway fe80::1

auto vmbr0
iface vmbr0 inet static
address 10.0.0.1/24
bridge-ports none
bridge-stp off
bridge-fd 0

post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up echo 1 > /proc/sys/net/ipv4/conf/eno1/proxy_arp
post-up iptables -t nat -A POSTROUTING -s '10.0.0.0/24' -o eno1 -j MASQUERADE
post-down iptables -t nat -D POSTROUTING -s '10.0.0.0/24' -o eno1 -j MASQUERADE
post-up iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 28967 -j DNAT --to 10.0.0.4:28967
post-up iptables -t nat -A PREROUTING -i vmbr0 -p udp --dport 28967 -j DNAT --to 10.0.0.4:28967
post-down iptables -t nat -D PREROUTING -i vmbr0 -p tcp --dport 28967 -j DNAT --to 10.0.0.4:28967
post-down iptables -t nat -D PREROUTING -i vmbr0 -p udp --dport 28967 -j DNAT --to 10.0.0.4:28967

iface vmbr0 inet6 static
address public.ipv6+1/64

iptables -L -t nat:
Chain PREROUTING (policy ACCEPT)
target prot opt source destination
DNAT tcp -- anywhere anywhere tcp dpt:28967 to:10.0.0.4:28967
DNAT udp -- anywhere anywhere udp dpt:28967 to:10.0.0.4:28967

Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

Chain POSTROUTING (policy ACCEPT)
target prot opt source destination
MASQUERADE all -- 10.0.0.0/24 anywhere

The eno1 interface was autogenerated by their installation script.
We added the bridge and the NAT etc.

Client config:
auto lo
iface lo inet loopback
iface lo inet6 loopback

auto eth0
iface eth0 inet static
address 10.0.0.4/24
gateway 10.0.0.1
pointtopoint public.ipv4

Client container has currently no firewall.

We are relatively inexperienced with networking inside a KWM host, so any help is greatly appreciated!

Proxmox port forwarding to Container behind NAT We have recently bought a server from the Hetzner server auction and want to migrate our previous root server. Previously we used only windows serve -

Stuck in terminal login page: I am trying to login to my Ubuntu system and every time I do this happens. I tried entering my login name and it doesn't work. I tried to enter commands but I couldn't. And I tried rebooting but it didn't work. How can I fix this? The image link is below

Stuck in terminal login page I am trying to login to my Ubuntu system and every time I do this happens. I tried entering my login name and it doesn't work. I tried to enter comma -

nginx load balancing without proxying trafic: I want to use nginx to load balance http traffic, but without proxying the traffic.

Like this user > lb > server > user

And not a standard proxy like

user > lb > server > lb > user

Is this possible or maybe I should look at another application?

nginx load balancing without proxying trafic I want to use nginx to load balance http traffic, but without proxying the traffic. Like this user > lb > server > user And not a standard p -